[
https://issues.apache.org/jira/browse/CASSANDRA-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871777#comment-17871777
]
Dmitry Konstantinov commented on CASSANDRA-19818:
-------------------------------------------------
Here a patch for trunk: [https://github.com/apache/cassandra/pull/3461]
Yes, I have a similar feeling, I am not insisting pushing it to 4.1 and 5.0
branches and open to the idea to have it in trunk only. At the same time taking
in account how long it took to get a production ready version for 5.0 I would
consider the ability to add such minor operational experience improvements to
production branches. It is simple and does not change any API.
> Minor improvements in Cassandra shutdown and startup logs
> ---------------------------------------------------------
>
> Key: CASSANDRA-19818
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19818
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
> Reporter: Dmitry Konstantinov
> Assignee: Dmitry Konstantinov
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To improve a DBA experience the following log messages would be nice to
> add/adjust:
> * on shutdown: an explicit message at the end of Cassandra shutdown
> * on startup:
> ** print the time spent to load prepared statements
> ** print the time spent to load repair session information and the number of
> loaded session records
> ** print the time spent to apply commit log
> It would help with assessment of possible delays in startup/shutdown of
> Cassandra. For example, recently I observed a delay in Cassandra startup and
> from logs it was not clear was it caused by loading of prepared statements or
> repair service init.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
