-
Notifications
You must be signed in to change notification settings - Fork 24
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
ChangeFeed Events seem to come in out of order #70
Comments
@Smithx10 CloudAPI should dispatch the VMAPI changefeed messages as they arrive. Can you take a look at CloudAPI/VMAPI logs and see if those are arriving in the right order, please? |
node-triton
CloudAPI
|
@Smithx10 This time those arrive in the right order, correct? The only thing I can see there is that it's translating Anyway, in order to check if the order of events looks like something unexpected, we should turn log level to trace on VMAPI, review the logs of the publisher there (which should just match with the client) and compare with vm-agent logs into the CN where the VM ins running. Wondering this might be due to small differences when updating object values in moray, but cannot be sure w/o all the info. |
@kusor I attempted to set vmapi loglevel to trace and didn't see any events or trace logs... only Info.
|
@Smithx10 if I'm not on a mistake you should either disable the config-agent service or modify the log level at |
It appears that the events aren't being sent in order, or are being sent out of order. The timestamps are a bit puzzling.
I believe the normal state changes would come in this order... shutting_down, down, stopped?
1st Stop
shutting_down, stopped, down
2nd Stop
stopped, down, shutting_down
The text was updated successfully, but these errors were encountered: