[
https://issues.apache.org/jira/browse/IGNITE-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862704#comment-16862704
]
Roman Shtykh commented on IGNITE-11771:
---------------------------------------
[~dmagda] sure. But I am not sure that having it enabled by default helps "to
avoid any issues with existing deployments."
In the current implementation (what we have in master branch),
`notReadyAddresses` are not included, right? If they started being included,
existing deployments might be surprised.
> Kubernetes discovery support for non-ready pods
> -----------------------------------------------
>
> Key: IGNITE-11771
> URL: https://issues.apache.org/jira/browse/IGNITE-11771
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.7
> Reporter: Balazs Peterfi
> Assignee: Denis Magda
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have a use case where Ignite is running in embedded mode and on start-up
> there is a time consuming task to warm-up the cache. During that time
> Kubernetes sees the pods as not ready due to the loading, thus the current
> implementation doesn't return them as potential members. Eventually they
> would become ready and see each-other but by then it would be a split-brain
> situation.
> The idea is to return IPs not only for "ready" pods but for "not ready" ones
> as well in case the discovery client is configured that way. See more details
> here:
> [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#endpointsubset-v1-core]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
