[
https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967801#comment-16967801
]
Tomas Eduardo Fernandez Lobbe commented on SOLR-13888:
------------------------------------------------------
Thanks for putting this together Mark. I agree with most of your points. One
thing I think we do want to work on sooner rather than later is modularization,
like Noble suggested. And I don’t know off the top of my head what those
modules need to be, but I feel building and testing separately is key to
maintain the code and tests in better shape.
bq. To replace ZooKeeper. To replace Http….
I agree that this is not the time to replace ZooKeeper, but a separated
“coordination” module that can be built and tested separately would be a huge
win IMO. If this allows us to run SolrCloud tests without having to fire a
ZooKeeper server, that would be fantastic. Also, it would allow people
developing different parts of Solr to not be expert in ZooKeeper internals. If
this is a first step to replace ZooKeeper, then so be it. And if the same can
be done, and have a transfer module, that would abstract communication between
nodes, maybe that’s a good idea too, I don’t know.
> 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
> Attachments: solrscreen.png
>
>
> 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
