[
https://issues.apache.org/jira/browse/IGNITE-23920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-23920:
---------------------------------------
Description:
I started ignite3db in the console. I then pressed Ctrl+C. The only line that
was added to the log was this:
2024-12-10 11:29:53:698 +0400 [INFO][Thread-1][Micronaut] Embedded Application
shutting down
It seems that IgniteServer#stop() was not called. We should call it before
exiting the process.
was:By default, RocksDB instances flush their changes to disk on shutdown,
and we don't disable this for the storage of the Metastorage. But sometimes it
can be seen that, on a start, a node replays Metastorage commands that were
already executed before, even if the node was stopped gracefully (and not
crashed). This means that either the storage was not flushed to disk on
shutdown, or that applied index (also stored in Metastorage's storage) does not
agree with the flushed data (this doesn't seem to be probable).
> Node is not stopped gracefully on SIGTERM
> -----------------------------------------
>
> Key: IGNITE-23920
> URL: https://issues.apache.org/jira/browse/IGNITE-23920
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> I started ignite3db in the console. I then pressed Ctrl+C. The only line that
> was added to the log was this:
> 2024-12-10 11:29:53:698 +0400 [INFO][Thread-1][Micronaut] Embedded
> Application shutting down
> It seems that IgniteServer#stop() was not called. We should call it before
> exiting the process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
