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

Stefan Miklosovic commented on CASSANDRA-14351:
-----------------------------------------------

If we want to try that library, somebody would need to test how good of a match 
it is for Cassandra. I briefly looked into the code of jsystemd and it is 
questionable how well it would integrate.

Also, one problem I see is that library is developed by one person only, even 
the project seems to be active.

The way I look at this is that it would be probably better if we introduce some 
well-rounded library with a proper releases etc rather than doing this by hand. 
On the other hand, if we do not plan to integrate with systemd more in the 
future, the proposed solution might be just fine as well.

> Support systemd SD_NOTIFY interface during startup
> --------------------------------------------------
>
>                 Key: CASSANDRA-14351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14351
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Thomas Bechtold
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When cassandra is started via systemd, it would be nice to support the 
> [SD_NOTIFY|https://www.freedesktop.org/software/systemd/man/sd_notify.html] 
> protocol so systemd know, when cassandra is ready (that can be use for 
> dependencies or when you need to wait until cassandra startup is done).
> A very simple implementation could be done using the 
> {code:java}
> systemd-notify --ready
> {code}
> command line tool (and ignore it if the tool is not there)



--
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