[
https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971823#comment-16971823
]
Gus Heck commented on SOLR-13888:
---------------------------------
Finally read all the way through this (a client was asking me about it) Some
thoughts:
# I think it's awesome that you have the energy and are given anything that
resembles the time to do this. We shouldn't throw shade on your passion.
# Since there's a rewrite underway, and I haven't seen it mentioned yet, one
of the cross cutting concerns that is on my wish-list is timeout sanity. (see
SOLR-13457). What I wrote there is probably entirely over ambitious, and
idealistic but those are the things I think would be nice to address.
# Totally understand not wanting to publish until you have something coherent,
the noise from the commentary on things you already know and plan to fix could
be deafening :). You know the risk of lost investment if folks disagree. We
don't have to be telling you this. For my part I'm curious, but patient since I
know I'll be unlikely to have the time to go through a large code drop in depth
any time soon anyway unless a client or two evaporate unexpectedly.
# You mentioned something I'm specifically interested in... Alias stuff
causing multiple updates. Can you elaborate? Even if your rewrite will blow it
away, incremental fixes or at least learning from it could be helpful.
> 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
