[
https://issues.apache.org/jira/browse/OAK-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938493#comment-16938493
]
Amit Jain edited comment on OAK-8593 at 9/27/19 6:06 AM:
---------------------------------------------------------
Done in trunk with [1867571|http://svn.apache.org/viewvc?rev=1867571&view=rev],
[1867618| http://svn.apache.org/viewvc?rev=1867618&view=rev]
UPDATE: Fixed IT
was (Author: amitjain):
Done in trunk with [1867571|http://svn.apache.org/viewvc?rev=1867571&view=rev]
> Enable a transient cluster-node to connect as invisible to oak discovery
> ------------------------------------------------------------------------
>
> Key: OAK-8593
> URL: https://issues.apache.org/jira/browse/OAK-8593
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Amit Jain
> Assignee: Amit Jain
> Priority: Major
> Fix For: 1.20.0
>
> Attachments: OAK-8593-2.patch, OAK-8593.patch
>
>
> Currently, if Oak is initialized with read-write access to the DocumentStore
> (Mongo/RDB) e.g through oak-run, it is made visible to upper layers (e.g.
> sling discovery) via the oak discovery cluster view. This can cause problems
> in the actual cluster with the differing topology view and the capabilities
> advertised and in some circumstances being made a leader.
> In an offline discussion with [~mreutegg] and [~stefanegli] it was decided
> that its best to expose a flag {{invisible}} in the cluserNodes
> collection/table with which these instances can connect and then these would
> be ignored by the oak discovery.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
