As you can see by all the bugs introduced by the recent large scale
refactorings around core container, the tests will not prevent this. SolrCloud
is even worse in this regard - many things are difficult to test or rely on
timing or this or that. We could use way more tests than we have and even
On 14 Dec 2013, at 19:58, Mark Miller wrote:
> I’ve looked at it over the years, but honestly, for most things, I don’t
> think switching would help much other than rewrite code that has been fairly
> hardened with fresh code that is just likely to introduce new bugs.
Well, that's what our com
I’ve looked at it over the years, but honestly, for most things, I don’t think
switching would help much other than rewrite code that has been fairly hardened
with fresh code that is just likely to introduce new bugs.
Targeted use of it for specific things could make sense, but that’s the type o
Evening all,
I discovered the Apache Curator project yesterday
(http://curator.apache.org/index.html), which seems to make interaction with
Zookeeper much easier. What do people think about using it for SolrCloud? In
particular, the LeaderLatch, Barrier and NodeCache recipes would make the
O
