On 4/13/15 5:31 PM, Stefan Egli stefane...@apache.org wrote:
PPS: I'll create another follow-up ticket for discovery which will be
about 'proper synchronizing between sending of topology_changed event and
the fact that the underlying repository is eventual consistent'. This
currently is
On 4/10/15 9:56 AM, Robert Munteanu romb...@apache.org wrote:
...I assume that this would
work with all DocumentNodeStore-based implementations, e.g. also with
the rdb mk. Is that assumption correct or do you plan a Mongo-only
implementation?
Yes that was the idea, to base it on
Hi Felix,
On 4/10/15 10:53 AM, Felix Meschberger fmesc...@adobe.com wrote:
* It depends on a specific implementation detail of a specific
Oak MK/NodeStore implementation. This implementation may
change at any time
* This feature seems to be accessed through JMX which exposes
and
well, that's an interesting approach, I'm curious to see how it'll work :)
Tommaso
2015-04-09 17:29 GMT+02:00 Stefan Egli stefane...@apache.org:
Hi all,
It has come up that with discovery.impl based on oak we could make use of
oak's (mongoMk's) lease mechanism instead of sending higher
Hi all,
It has come up that with discovery.impl based on oak we could make use of
oak's (mongoMk's) lease mechanism instead of sending higher level
heartbeats.
I've created SLING-4603 to track that and would appreciate some opinions
from this list. I'd be looking at providing a first
