You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Amrit Sarkar (JIRA)" <ji...@apache.org> on 2018/12/11 18:15:00 UTC

[jira] [Resolved] (SOLR-13055) Introduce check to determine "liveliness" of a Solr node

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

Amrit Sarkar resolved SOLR-13055.
---------------------------------
    Resolution: Duplicate

> Introduce check to determine "liveliness" of a Solr node
> --------------------------------------------------------
>
>                 Key: SOLR-13055
>                 URL: https://issues.apache.org/jira/browse/SOLR-13055
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Amrit Sarkar
>            Priority: Minor
>              Labels: cloud, native
>
> As the applications are becoming cloud-friendly; there are multiple probes which are required to verify availability of a node.
> Like in Kubernetes we need 'liveliness' and 'readiness' probe explained in https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/n determine if a node is live and ready to serve live traffic.
> Solr should also support such probes out of the box as an API or otherwise to make things easier. In this JIRA, we are tracking the necessary checks we need to determine if a node is  'liveliness', in all modes, standalone and cloud.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org