I see two orthogonal aspects discussed here:
- How/where state is tracked (e.g. state.json, PRS directory structure)
- How/from where state is updated (Overseer vs distributed, PRS works with
either mode)
I think a desirable future has a more efficient state tracking adapted to
the actual state ac
It’s hard to see how they are not related. You can look at both as trying
to solve largely the same problem - that the Overseer is mind boggling
inefficient. And it’s hard to see how pursuing one makes sense with the
other. If you were to eliminate the Overseer and essentially distribute
most of it
I think we should have separate threads for these two topics. I'll start a
new thread for Distributed State Updates vs Overseer. If they become
related for certain points then they can be raised here?
On Wed, Sep 21, 2022 at 11:44 AM Houston Putman wrote:
> Hey everyone,
>
> We've seen some i
Hey all,
I'm a long time Solr user/developer, but only recently joined the dev
mailing list for Solr so it is a pleasure to interact with you all.
We, at FullStory, working with Ishan and Noble, sponsored the Per Replica
State implementation and are using it currently. We are running large
cluste
Hey everyone,
We've seen some interesting developments over the last 2 years in the way
that Solr state and distributed logic is handled. Notably we've seen the
introduction of PerReplicaStates (PRS) and the Distributed State Updates
(no overseer).
I think for the health of our code and future ma
