t;> problem.
>>>>>>>>>>>
>>>>>>>>>>> But Solr has as many problems as SolrCloud at this point. This
>>>>>>>>>>> just mater a whole hell of lot less unless they are messing with
>>>>>
>>>> SolrCloud. Standalone is more of a brute.
>>>>>>>>>>
>>>>>>>>>> We have 60 modules that are interconnected. We have a huge code
>>>>>>>>>> base. That is also fine.
>>>>>>>&g
>>>>>>
>>>>>>>>> Anyway, no redesign, no library, no nothing like that gonna save
>>>>>>>>> this.
>>>>>>>>>
>>>>>>>>> This is hardly concrete awareness of a problem here. The awar
en.
>>>>>>>>> You
>>>>>>>>> guys only get to see it grown over and full of weeds.
>>>>>>>>>
>>>>>>>>> Anyway, no redesign, no library, no nothing like that gonna save
>&g
ss
>>>>>>>> to figure out what actually are the problems and what must be done -
>>>>>>>> that's
>>>>>>>> expensive shit these days if you ask me. I've been wrong lots tough.
>>>>>>>>
>>>>&
te:
>>>>>>>
>>>>>>>> I guess this is also a bit normal with software that grows over the
>>>>>>>> years.
>>>>>>>> One could also say that one writes the current use cases and
>>>>>>&
t; maintain both - but this will be also the case for a major rewrite.
>>>>>>>
>>>>>>> > Am 04.11.2019 um 20:58 schrieb Erick Erickson <
>>>>>>> erickerick...@gmail.com>:
>>>>>>> >
>>>>>>> > If
>
>>>>>> > But yeah, a nifty, new, more modern tool isn’t going to magically
>>>>>> help if the design is flawed.
>>>>>> >
>>>>>> > Or, if I’m putting my philosophical hat on, code doesn’t get gnarly
>>>>>> intentionally. I
f the design is flawed.
>>>>> >
>>>>> > Or, if I’m putting my philosophical hat on, code doesn’t get gnarly
>>>>> intentionally. It gets gnarly because there are a bunch of problems to be
>>>>> solved and you don’t know what they ar
’s own
>>>> weight and becomes increasingly fragile and you must take the hit and redo
>>>> major portions of it. The questions now are:
>>>> > 1> are we at that point?
>>>> > 2> are we going to put the effort into rewriting some of the w
gt;> >
>>> >
>>> >> On Nov 4, 2019, at 1:28 PM, Scott Blum wrote:
>>> >>
>>> >> Figuring out a better overall algorithmic & data structure design
>>> that's an order of magnitude improvement seems far more important tha
gt; swapping out libraries. And I say this as a Curator fan and committer. ;)
>> >>
>> >> On Mon, Nov 4, 2019 at 11:44 AM Erick Erickson <
>> erickerick...@gmail.com> wrote:
>> >> Bram:
>> >>
>> >> Using Curator has been proposed
son
> wrote:
> >> Bram:
> >>
> >> Using Curator has been proposed before. It would require significant
> refactoring b/c of how deeply entwined raw ZK is in the code. That said, if
> we’re going to do major surgery it may be the right time to consider it.
> >>
&g
g Curator has been proposed before. It would require significant
>> refactoring b/c of how deeply entwined raw ZK is in the code. That said, if
>> we’re going to do major surgery it may be the right time to consider it.
>>
>> Erick
>>
>>>> On Nov 4, 2019, at 9:
en proposed before. It would require significant
> refactoring b/c of how deeply entwined raw ZK is in the code. That said, if
> we’re going to do major surgery it may be the right time to consider it.
>
> Erick
>
> > On Nov 4, 2019, at 9:24 AM, Bram Van Dam wrote:
> >
Using Curator has been proposed before. It would require significant
> refactoring b/c of how deeply entwined raw ZK is in the code. That said, if
> we’re going to do major surgery it may be the right time to consider it.
>
> Erick
>
> > On Nov 4, 2019, at 9:24 AM, Bram Van
ote:
>
>> SolrCloud is sick right now. The way low level Zookeeper is handeled
>
> On an unrelated project, I've stopped using "raw" ZK client access and
> have switched to Curator. The API is a fair bit easier to work with, and
> it results in less ugly code. I realize tha
> SolrCloud is sick right now. The way low level Zookeeper is handeled
On an unrelated project, I've stopped using "raw" ZK client access and
have switched to Curator. The API is a fair bit easier to work with, and
it results in less ugly code. I realize that this won't g
y XML parser
> processing file://lucene/src/main/xml/ENTITY_TermQuery.xml: www.bar.xyz:
> Unknown host www.bar.xyz
> ]>
>
> apparently www.bar.xyz host is supposed to be a placeholder
> but for the life of me I cannot see where www.bar.zyz placeholder is replaced
> by
;
placeholder is replaced by a valid URL
(i havent used DTD in at least 10 years and i am way out of my element when
trying to resolve)
any suggestions?
martin
From: David Smiley
Sent: Sunday, November 3, 2019 12:32 AM
To: Solr/Lucene Dev
Cc: Mark Miller
Subject:
>>> huge technical debt.
>>>>> >>>
>>>>> >>>
>>>>> >>> This is not to put blame on one person or a group of people. (I
>>>>> occasionally see people discussing design issues upfront, I just hope that
>>>>> i
;> >>> While we agree there are problems, we are trying to solve the
>>>> problem using the same process we used to create these problems. Again, I'm
>>>> not questioning the intent or competence of anyone. Unless we set the
>>>> process right, we ar
rough meaningful discussion.
>>> >>>
>>> >>>
>>> >>> I hope we don't resort to personal attacks and use this as an
>>> opportunity to improve our processes.
>>> >>> Thanks
>>> >>>
>>> >>> On
>> >>>
>> >>> On Sun, Nov 3, 2019, 9:52 AM Scott Blum
>> wrote:
>> >>>>
>> >>>> Very much agreed. I've been trying to figure out for a long time
>> what is the point in having a replica DOWN state that has to be
ve_nodes` to understand whether a replica is
> available. It's not even foolproof since kill -9 on a solr node won't mark
> all the replicas DOWN-- that doesn't happen until the node comes back up
> (perversely).
> >>>>
> >>>> What would it take to g
WN-- that doesn't happen until the node comes back
>>>> up (perversely).
>>>>
>>>> What would it take to get to a state where restarting a node would require
>>>> a minimal amount of ZK work in most cases?
>>>>
>>&
wrote:
>>>>
>>>> Give me a short bit to follow up and I will lay out my case and proposal.
>>>>
>>>> Everyone is then free to decide that we need to do something drastic or
>>>> that I'm wrong and we should just continue down the same road. If
e same road. If that's
>>> the case, a lot of your work will get a lot easier and less impeded by me
>>> and we will still all be happier. Win win.
>>>
>>> If we can just not make drastic changes for a just a brief week or so
>>> window, I'll say wha
case and
>>>>> proposal.
>>>>>
>>>>> Everyone is then free to decide that we need to do something drastic
>>>>> or that I'm wrong and we should just continue down the same road. If
>>>>> that's
>>>>> the ca
e should just continue down the same road. If that's
>>>> the case, a lot of your work will get a lot easier and less impeded by me
>>>> and we will still all be happier. Win win.
>>>>
>>>> If we can just not make drastic changes for a just
t; and we will still all be happier. Win win.
>>>
>>> If we can just not make drastic changes for a just a brief week or so
>>> window, I'll say what I have to say, you guys can judge and do whatever
>>> you'd please.
>>>
>>> - mark
>
for a just a brief week or so
>> window, I'll say what I have to say, you guys can judge and do whatever
>> you'd please.
>>
>> - mark
>>
>> On Fri, Nov 1, 2019 at 7:46 PM Mark Miller wrote:
>>
>>> Hey All Solr Dev's,
>>>
>&g
eryone is then free to decide that we need to do something drastic or
>>> that I'm wrong and we should just continue down the same road. If that's
>>> the case, a lot of your work will get a lot easier and less impeded by me
>>> and we will still all be happier.
er and less impeded by me
>> and we will still all be happier. Win win.
>>
>> If we can just not make drastic changes for a just a brief week or so
>> window, I'll say what I have to say, you guys can judge and do whatever
>> you'd please.
>>
>&g
ease.
>
> - mark
>
> On Fri, Nov 1, 2019 at 7:46 PM Mark Miller wrote:
>
>> Hey All Solr Dev's,
>>
>> SolrCloud is sick right now. The way low level Zookeeper is handeled, the
>> Overseer, is mix and mess of proper exception handling and super slow
>&
by me
and we will still all be happier. Win win.
If we can just not make drastic changes for a just a brief week or so
window, I'll say what I have to say, you guys can judge and do whatever
you'd please.
- mark
On Fri, Nov 1, 2019 at 7:46 PM Mark Miller wrote:
> Hey All Solr Dev
Hey All Solr Dev's,
SolrCloud is sick right now. The way low level Zookeeper is handeled, the
Overseer, is mix and mess of proper exception handling and super slow
startup and shutdown, adding new things all the time with no concern for
performance or proper ordering (which is harder to tell
37 matches
Mail list logo