Thanks. Features lists are as hard as time frames. I keep a boat load of
various experiments and dead ends and potential on the side that would just
muddy the waters until the basics are right. And the basics take 95% of the
time and effort. So it’s 11:59 pm before I know what gets pulled out, say
This is the most comprehensive list of improvements we've seen so far. I
know from our conversations having discussed many of these goals, but I'm
glad to see them here as a list.
Thanks for your work, Mark!
On Sat, Apr 24, 2021 at 11:05 PM Mark Miller wrote:
> *Ive taken a step back on this bra
*Ive taken a step back on this branch for a bit as I engage in other things
and catch a breath.*
Before I dump some of my notes on the background of some of the
technical stuff, I’ll likely make it a bit easier to take the branch for a
spin and put up the remaining code I have.
The branc
Things are for all intents and purposes, at the point where my train
stops. The next sensible train is likely, really the one you wanted to
board. And that is looking at what short term value and experiments and
results can likely be harnessed and converted from the issues I create in a
fork into
As I think about the question of “What is the priority of this Solr2 stuff,
addressing the immediate issues in Solr or performance?” It triggers all
kinds of responses from me, because the two are so wrapped up.
But I’m gonna take a guess and say maybe the question is more like:
I’m using Solr
Anyway, like I said, my thoughts and notes on a Solr 2 will arrive shortly.
They don’t involve release planning or branching or how one might go about
an effort larger than a typical incremental release.
For those I gave a date for those notes and comments, I apologize for being
late. Life I guess
t;>>>>>> I'm gonna link bombs and jet around a bit.
>>>>>>>>>
>>>>>>>>> Let's kind of root of this at "shards with no leader, replicas not
>>>>>>>>> recovering, non functional Overseer etc"
>>>&
many
>>>>>>>> necessary
>>>>>>>> improvements without it at least semi solid. You can't obtain
>>>>>>>> reliability
>>>>>>>> and greatness without it being ridiculously solid. To test and verify
>>&g
gt;>>>>>> explore that, you'll have quite a challenge avoiding joining my
>>>>>>> contest. So
>>>>>>> it's a good lead. But also, it's an undercurrent through the system. The
>&
fferent ways, keeping things,
>>>>>> removing things, changing things - you could do it many ways. "The
>>>>>> overseer
>>>>>> is not the problem", it must sound funny to you. But the Overseer as a
>>>>>> concept has n
ot the problem", it must sound funny to you. But the Overseer as a
>>>>> concept has no problem. Even the poor current design can essentially work.
>>>>> 30 designs can work better, other designs can work too. The root issues
>>>>> around it don
designs can work too. The root issues
>>>> around it don't stop at its borders. Anyway, let's do it. I'll dump the
>>>> path here. Let's try to blast a litte.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
gt;
>>>
>>>
>>>
>>>
>>>
>>>
>>>>
>>> On Sun, Apr 11, 2021 at 7:16 AM Ilan Ginzburg
>>>> wrote:
>>>>
>>> Do you consider performance/scale of SolrCloud or corectness (shards
>>>>&
;>
>>
>>
>>
>>
>>
>>>
>> On Sun, Apr 11, 2021 at 7:16 AM Ilan Ginzburg wrote:
>>>
>> Do you consider performance/scale of SolrCloud or corectness (shards with
>>>> no leader, replicas not recovering, non functional Overseer etc) as the
>&g
ds with
>>> no leader, replicas not recovering, non functional Overseer etc) as the
>>> most important areas for improvement if we were to move to a v2?
>>>
>>>
>>> Ilan
>>>
>>> Le sam. 10 avr. 2021 à 22:37, Mark Miller a
>>> écrit
gt;> no leader, replicas not recovering, non functional Overseer etc) as the
>> most important areas for improvement if we were to move to a v2?
>>
>>
>> Ilan
>>
>> Le sam. 10 avr. 2021 à 22:37, Mark Miller a
>> écrit :
>>
>>&
e to a v2?
>
>
> Ilan
>
> Le sam. 10 avr. 2021 à 22:37, Mark Miller a
> écrit :
>
>> Now a I was saying ... SolrCloud2. Well, some people don’t like the name
>> - fair enough - I don’t like purple much and I didn’t invent either... so
>> Solr2.
>>
>>
t :
>
>> Now a I was saying ... SolrCloud2. Well, some people don’t like the name
>> - fair enough - I don’t like purple much and I didn’t invent either... so
>> Solr2.
>>
>>
>>
>> I have some thoughts, a few things to offer. Yes, the guy behind a lot of
>&g
ing ... SolrCloud2. Well, some people don’t like the name -
> fair enough - I don’t like purple much and I didn’t invent either... so
> Solr2.
>
>
>
> I have some thoughts, a few things to offer. Yes, the guy behind a lot of
> the current garbage. They asked me my thoughts on this thi
Now a I was saying ... SolrCloud2. Well, some people don’t like the name -
fair enough - I don’t like purple much and I didn’t invent either... so
Solr2.
I have some thoughts, a few things to offer. Yes, the guy behind a lot of
the current garbage. They asked me my thoughts on this thing on day
20 matches
Mail list logo