[
https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965209#comment-16965209
]
Shawn Heisey commented on SOLR-13888:
-------------------------------------
* I don't care too much whether we still call it SolrCloud or migrate to
calling it cluster mode. And I think that's a separate discussion, affecting
documentation more than anything.
* I do not know the code that drives this. I'd like to understand the code,
but I'm betting that that rabbit hole will take me at least a few weeks to
traverse ... assuming I devote ALL of my spare time to it. That is something
that I just can't do right now.
* I do know from mailing list threads and user-filed issues that we have users
who have tons of stability problems with SolrCloud, and those are affecting
even users who haven't built massive clusters.
> SolrCloud 2
> -----------
>
> Key: SOLR-13888
> URL: https://issues.apache.org/jira/browse/SOLR-13888
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
