[
https://issues.apache.org/jira/browse/CASSANDRA-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872357#comment-17872357
]
Stefan Miklosovic commented on CASSANDRA-19818:
-----------------------------------------------
I think the easiest way to solve this would be to leave out changes related to
LocalSessions.
> 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: 5.0.x, 5.x
>
> Time Spent: 50m
> 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]
