[jira] [Updated] (CASSANDRA-13493) RPM Init: Service startup ordering
[ 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13493) RPM Init: Service startup ordering
[ https://issues.apache.org/jira/browse/CASSANDRA-13493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-13493: --- Status: Ready to Commit (was: Patch Available) > 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 > Fix For: 3.11.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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13493) RPM Init: Service startup ordering
[ https://issues.apache.org/jira/browse/CASSANDRA-13493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] martin a langhoff updated CASSANDRA-13493: -- Attachment: 0001-RPM-Init-ordering-start-after-network-and-name-servi.patch > 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 > Fix For: 3.11.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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13493) RPM Init: Service startup ordering
[ https://issues.apache.org/jira/browse/CASSANDRA-13493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] martin a langhoff updated CASSANDRA-13493: -- Reviewer: Michael Shuler Fix Version/s: 3.11.0 Status: Patch Available (was: Open) > 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 > Fix For: 3.11.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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org