Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
As devs discuss dropping the SolrCloud name on the dev list, here is an issue titled SolrCloud 2.
A couple times now I've pulled on the sweater thread that is our broken tests. It leads to one place - SolrCloud is sick and devs are adding spotty code on top of it at a rate that will lead to the system falling in on itself. As it is, it's a very slow, very inefficient, very unreliable, very buggy system.
This is not why I am here. This is the opposite of why I am here.
So please, let's stop. We can't build on that thing as it is.
I need some time, I lost a lot of work at one point, the scope has expanded since I realized how problematic some things really are, but I have an alternative path that is not so duct tape and straw. As the building climbs, that foundation is going to kill us all.
This i not about an architecture change - the architecture is fine. The implementation is broken and getting worse.
