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 searched in the issues and found nothing similar.
Version
iotdb 1.3.1-standalone
Describe the bug and provide the minimal reproduce step
When stoping a docker container running the apache/iotdb:1.3.1-standalone image the SIGTERM signal handling trap is not executed leading to a non graceful shut down. This is because the entrypoint.sh script uses exec which destroys signal handlers using trap.
Furthermore, the function that should be executed at SIGTERM 'on_stop' defined in entrypoint.sh has the if statement "$start_what" != "all".` Therfore in standalone mode the corresponding graceful shutdown is not executed.
To reproduce run the docker container and then stop it.
What did you expect to see?
The on_stop function defined in entrypoint.sh is executed when the docker container is stopped providing a graceful shutdown with FLUSH.
What did you see instead?
Rapid shut down without proper SIGNAL handling and without execution of the on_stop function.
Anything else?
No response
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Version
iotdb 1.3.1-standalone
Describe the bug and provide the minimal reproduce step
When stoping a docker container running the apache/iotdb:1.3.1-standalone image the SIGTERM signal handling trap is not executed leading to a non graceful shut down. This is because the entrypoint.sh script uses
exec
which destroys signal handlers usingtrap.
Furthermore, the function that should be executed at SIGTERM 'on_stop' defined in entrypoint.sh has the if statement
"$start_what"
!= "all".` Therfore in standalone mode the corresponding graceful shutdown is not executed.To reproduce run the docker container and then stop it.
What did you expect to see?
The on_stop function defined in entrypoint.sh is executed when the docker container is stopped providing a graceful shutdown with FLUSH.
What did you see instead?
Rapid shut down without proper SIGNAL handling and without execution of the on_stop function.
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: