You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a driver plugin and i miss stats if the plugin dies and restarts.
My plugin reports stats fine when a task is initially started. So i can see in the logs that "TaskStats" is called and i can watch metrics in the nomad web-ui.
Now, if i kill the plugin process (not nomad itself!) in order to simulate a crash, i can see that "RecoverTask" is invoked. The callback is handled well and i am able to control the task just fine.
"TaskStats", however, is not called after recovery and thus the plugin does not stream stats into nomad resulting in a stuck graph in the UI.
The text was updated successfully, but these errors were encountered:
Thanks for checking!
Killing a plugin process is actually a nice shortcut for updating a plugin while working on the code base. It's much quicker compared to restarting a nomad agent. Automatic task recovery ensures a consistent in-memory state as well.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Nomad v0.9.3 (c5e8b66)
Operating system and Environment details
Ubuntu 18.04
Issue
I am working on a driver plugin and i miss stats if the plugin dies and restarts.
My plugin reports stats fine when a task is initially started. So i can see in the logs that "TaskStats" is called and i can watch metrics in the nomad web-ui.
Now, if i kill the plugin process (not nomad itself!) in order to simulate a crash, i can see that "RecoverTask" is invoked. The callback is handled well and i am able to control the task just fine.
"TaskStats", however, is not called after recovery and thus the plugin does not stream stats into nomad resulting in a stuck graph in the UI.
The text was updated successfully, but these errors were encountered: