syndic architecture does not scale #67616
Replies: 5 comments
-
I believe that this may be improved in the deltaproxy work that @garethgreenaway is working on. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Beta Was this translation helpful? Give feedback.
-
solution is quite simple to this for list targeting. @garethgreenaway can you please comment if I should close the ticket or keep it open ? |
Beta Was this translation helpful? Give feedback.
-
Thank you for updating this issue. It is no longer marked as stale. |
Beta Was this translation helpful? Give feedback.
-
At this time @tsaridas the Core team won't be working on scaling the syndic architecture in salt, you can find this in our Enterprise solution or you can open a PR for review. I will leave this open, and the Stale bot configuration will skip it with the label |
Beta Was this translation helpful? Give feedback.
-
Description of Issue
When having multiple syndics with a large number of minion connecting to different syndics saltstack syndic tries to send commands (tcp connection to salt-master) for all of them even if the minion does not exist.
After syndic sends the command then salt-master does figure out which minions are but this is not very performant.
I suggest to check if master has the minion key on the salt-syndic at least for targeting with list so that syndic avoids connecting to salt-master.
The performance issue does not show with small number of minions.
Setup
salt-master (mom) -> syndic -> minion
Steps to Reproduce Issue
not applicable
Versions Report
All versions
Beta Was this translation helpful? Give feedback.
All reactions