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
As it stands, when the system test shuts down a KS service, the service doesn't complete shutting down cleanly.
The ProcessorStateManager class in streams is calling:
checkpointFile.write(checkpointingOffsets);
Which kind of blocks... ish... but not. There aren't any checkpoints to write, and the state.dir doesn't exist. Yet the call blocks for 10+ seconds. After which, the JVM shuts down.
The System test executor has a 30s timeout for graceful shutdown and this is not hit.
The streams app defaults to a 30s timeout for graceful shutdown, and this isn't hit either.
So actually not sure what is causing it to shutdown.
However, as we haven't yet written the code for adding mount points for state to KS apps... maybe its something to do with that.
The text was updated successfully, but these errors were encountered:
As it stands, when the system test shuts down a KS service, the service doesn't complete shutting down cleanly.
The
ProcessorStateManager
class in streams is calling:Which kind of blocks... ish... but not. There aren't any checkpoints to write, and the
state.dir
doesn't exist. Yet the call blocks for 10+ seconds. After which, the JVM shuts down.The System test executor has a 30s timeout for graceful shutdown and this is not hit.
The streams app defaults to a 30s timeout for graceful shutdown, and this isn't hit either.
So actually not sure what is causing it to shutdown.
However, as we haven't yet written the code for adding mount points for state to KS apps... maybe its something to do with that.
The text was updated successfully, but these errors were encountered: