cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13493) RPM Init: Service startup ordering
Date Thu, 18 May 2017 18:01:04 GMT

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

Stefan Podkowinski updated CASSANDRA-13493:
-------------------------------------------
       Resolution: Fixed
         Assignee: Stefan Podkowinski
    Fix Version/s: 4.0
                   3.0.14
                   2.2.10
           Status: Resolved  (was: Ready to Commit)

Merged as dd6aa991b33caef4c1b6f2b5bc5ef3237cb87865

> RPM Init: Service startup ordering
> ----------------------------------
>
>                 Key: CASSANDRA-13493
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13493
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Packaging
>            Reporter: martin a langhoff
>            Assignee: Stefan Podkowinski
>             Fix For: 2.2.10, 3.0.14, 3.11.0, 4.0
>
>         Attachments: 0001-RPM-Init-ordering-start-after-network-and-name-servi.patch
>
>
> Currently, Cassandra is setup to start _before_ network and name services come up, and
setup to be town down _after_ them, dangerously close to the final shutdown call.
> A service daemon which may use network-based storage, and serves requests over a network
needs to start clearly after network and network mounts, and come down clearly after.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message