lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Robert Miller (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-13888) SolrCloud 2
Date Fri, 08 Nov 2019 15:14:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970257#comment-16970257
] 

Mark Robert Miller edited comment on SOLR-13888 at 11/8/19 3:13 PM:
--------------------------------------------------------------------

I'll even give you more. I wish just telling the problems *WAS* all I had to do:

Some alias stuff makes cluster state updates notifications fire twice in a row.

There is bad concurrency in a lot of spots, just spot check.

There is a lot of bad exception handling and interruption handling that are actually very
important.

There a lot of bad behavior in failure cases, if you make it better, fails get easier to look
at.

There is a lot of weird and off stuff in the collections api, because it's trying to balance
two worlds, its not well tests, and other things.

Our base layer zk stuff, like the mkpaths and retry stuff, can do weird.

Lots of times we dont handle session expiration.

 

I'll give you more too ....there is a lot more hours there. When will you start?

 


was (Author: markrmiller):
I'll even give you more. I wish just telling the problems *WAS* all I had to do:

Some alias stuff makes cluster state updates fire twice in a row.

There is bad concurrency in a lot of spots, just spot check.

There is a lot of bad exception handling and interruption handling that are actually very
important.

There a lot of bad behavior in failure cases, if you make it better, fails get easier to look
at.

There is a lot of weird and off stuff in the collections api, because it's trying to balance
two worlds, its not well tests, and other things.

Our base layer zk stuff, like the mkpaths and retry stuff, can do weird.

Lots of times we dont handle session expiration.

 

I'll give you more too ....there is a lot more hours there. When will you start?

 

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


Mime
View raw message