-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sqs_events: SQS messages processed before reactor engine is ready #49404
Comments
ping @saltstack/team-core any ideas on how to solve the issue where hte engine and events start sending before the reactor is up |
We would need to add the ability to order the starting of engines. To make sure the reactor engine is up before the sqs engine. |
hi team, any update on this issue ? i am facing the same problem. Dependency Versions: System Versions: |
afaik there is no work currently being done allowing ordering of engine starts. But you could try directly specifying the reactor in the list of engines.
And see if explicitly putting the reactor engine before the sqs events engine causes the reactor to be started first. The way that the reactor is started now is if you have a |
@gtmanfred thanks |
nope, it would require a change to allow for ordering of the engines to start, and something to signify that an engine has finished starting before the next one is started. and that would be a feature request if @saltstack/team-triage will tag it. thanks |
thanks, Daniel,
it would be great if @saltstack/team-triage
<https://github.com/orgs/saltstack/teams/team-triage> can tag it and
provide a solution/fix at the earliest.
|
Since this is asking for new functionality, the ability to specify some dependencies in what order engines load, which doesn't currently exist I'll go ahead and label it as a feature request and approve it for a future feature addition. |
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. |
Still valid |
Thank you for updating this issue. It is no longer marked as stale. |
Description of Issue/Question
See also: https://groups.google.com/forum/#!topic/salt-users/tAm-c-Cs5ss
We are using the sqs_events engine but we are losing messages.
When Salt is starting, sqs_events engine is ready and starts to send events before the reactor engines is properly started.
I also test to sleep a bit at the beginning of the
start
function of the sqs_events engine.With this, messages are not lost at startup anymore but we are still losing messages when restarting so it seems that when Salt is stopping, events may be sent when reactors are already stopped.
Test setup
For testing purpose, I've just created a reactor which creates empty files with filenames retrieved for the SQS queue and I'm sending messages in the queue manually.
Master configuration (relevant part):
states/test_sqs_events.sls
Steps to Reproduce Issue
The first test is to stop salt-master, then to run
Then to start salt-master
No messages will be processed by reactors:
Logs (relevant part)
Restart
If we test to restart salt-master during message sending:
Then just after messages started to be sent:
We can see that some messages have been lost:
Versions Report
(also tested on Salt 2016.11.X)
The text was updated successfully, but these errors were encountered: