cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14875) Explicitly initialize StageManager early in startup
Date Fri, 16 Nov 2018 04:03:00 GMT

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

C. Scott Andreas updated CASSANDRA-14875:
-----------------------------------------
    Component/s: Lifecycle

> Explicitly initialize StageManager early in startup
> ---------------------------------------------------
>
>                 Key: CASSANDRA-14875
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14875
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Lifecycle
>            Reporter: Aleksandr Sorokoumov
>            Assignee: Aleksandr Sorokoumov
>            Priority: Minor
>             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
(v7.6.3#76005)

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


Mime
View raw message