[ 
https://issues.apache.org/jira/browse/CASSANDRA-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872134#comment-17872134
 ] 

Dmitry Konstantinov commented on CASSANDRA-19818:
-------------------------------------------------

Please find examples of the added/modified log messages below:
{code:java}
INFO  [StorageServiceShutdownHook] 2024-08-08 21:18:15,578 
StorageService.java:732 - Cassandra shutdown complete {code}
{code:java}
INFO  [main] 2024-08-08 21:16:02,597 CommitLog.java:210 - Log replay complete, 
90 replayed mutations in 1259 ms
{code}
{code:java}
INFO  [main] 2024-08-08 21:16:03,139 LocalSessions.java:391 - LocalSessions 
start completed in 3 ms, sessions loaded from DB: 0
{code}
{code:java}
INFO  [main] 2024-08-08 21:16:03,149 QueryProcessor.java:210 - Preloaded 1 
prepared statements in 8 ms
{code}
{code:java}
WARN  [main] 2024-08-08 21:41:51,088 QueryProcessor.java:204 - Prepared 
statement recreation error, removing statement: 
97271bbb319084a8749af2b52428ec51 INSERT INTO memory_tests.test_table_text_0 
(part_key,clust_key,udt_value) VALUES (?,?,?) null, error details: Undefined 
column name udt_value in table memory_tests.test_table_text_0
{code}

> 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: 0.5h
>  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]

Reply via email to