You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2020/02/27 04:01:00 UTC

[jira] [Updated] (CASSANDRA-14875) Explicitly initialize StageManager early in startup

     [ https://issues.apache.org/jira/browse/CASSANDRA-14875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Dimitrova updated CASSANDRA-14875:
--------------------------------------------
    Reviewers: Ekaterina Dimitrova, Ekaterina Dimitrova  (was: Ekaterina Dimitrova)
               Ekaterina Dimitrova, Ekaterina Dimitrova
       Status: Review In Progress  (was: Patch Available)

> Explicitly initialize StageManager early in startup
> ---------------------------------------------------
>
>                 Key: CASSANDRA-14875
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14875
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Startup and Shutdown
>            Reporter: Aleksandr Sorokoumov
>            Assignee: Aleksandr Sorokoumov
>            Priority: Low
>             Fix For: 4.x
>
>
> {{StageManager}} initializes itself through a static block and sets up every {{Stage}}, including pre-starting their threads. This initizalization can take a few hundred milliseconds. This timing impact is unpredictable and hard to reason about; it looks like it usually gets hit when creating new Keyspaces on start-up and announcing them through migrations.
> While these processes are resilient to these delays, it is dramatically easier to reason about over time if this initialization happens explicitly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org