Anyway, that’s just a bit of context.  What and how and when a Solr 2 could
be and work and coexist and share with what we have is hugely available and
flexible issue - if I’m talking about o serious collaborators. Almost as
flexible and open to possibility as software itself.

And I’ve got plenty coming very very soon that’s organized and approachable
and picky eater edible.  So no reason to get bogged down first.

But also id like to say, that question is not anywhere near the trade off
you think it is. Try to avoid huge gains in both with simple potent
strikes. Not the issue. Until I have to resort to huge, aggressive scale
and performance, no thinking about that trade.  Both will rise on anything
good. Let’s discuss that a little. I’ll put something together.

Beyond that - and there is work and time between us and beyond that - but
beyond that, is where the interesting field lies. The point that hardware
and inefficiency gets routed. Enemy
ambushes deep in victory territory?!

Now we can author the book backwards.  You tell me.

Does that mean we don’t peak at the end? Discuss the end? hang the time in
the sqaure before he messed up the timeline?

Who knows.  But that is where this project needs to move too. And more
offensive and laughter - but in limited time. Because projects are being
built working on those problems while projects like ours can’t even look at
them yet.  I’m not taking a keep when I say time is limited. It’s just
obvious nature as you peel around at the state of things.



On Sun, Apr 11, 2021 at 7:16 AM Ilan Ginzburg <[email protected]> wrote:

> Do you consider performance/scale of SolrCloud or corectness (shards 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 <[email protected]> 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.
>>
>>
>>
>> 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 one - I
>> told them I don’t have a single one, let me have a go and I’ll get back to
>> you. Done and done.
>>
>>
>> So yeah, Solr2. Wait, what’s that ... ? Loud dance floor out here - if I
>> could have the floor for just a moment. I’ve put just a little bit of time
>> and effort in before grabbing the mic. A modicum. My ego, my job, my
>> status, my history, really not part of the equation, so if I could request
>> a few lines before the rebuttal and correction and redirection.  No
>> hurry for those things, they are patient characters.
>>
>>
>> Anyway, give me a moment, and in return I’ll spare you the long winded
>> diversions.
>>
>>
>> Having considered Solr2 for some time, I see all kinds of roadblocks and
>> restraints and limitations. I see a path fraught with the potential to
>> mimic previous paths. And my goodness, I’m getting old. Fresh, promising
>> paths please. So Ive invested some time and effort to establish an escape
>> route from the safe, conservative hack and slash through the jungle that
>> gets less safe the deeper we dive. I’d simply tell you about it, but jungle
>> stories are all heart and no soul and we will all trade them all day.
>>
>>
>> So I’ve got some notes and code and maps and journals and crap instead.
>> Compiled from a couple expeditions. From before spelunking made me an old
>> man. So my machete isn’t solo diving any new trails, single handedly
>> slaying jungle cats any longer. The blade just keeps getting duller.
>>
>>
>> But I’ve got these previous materials. I’ll lay them out. Take a look. If
>> we can explore and discuss with just a passing courtesy of respect for our
>> relative time and investment and focus put in before letting loose, I’m
>> sure we can move beyond basic software counter meandering quickly enough to
>> actually enter the jungle.
>>
>>
>> I’ll try and lay out some evidence to help here. For instance, that
>> zookeeper is not the issue. That the overseer is not the issue. That
>> modules and multitudes of features are not the issue. Previous efforts are
>> not the issue. Object oriented development and agile frameworks are not the
>> issue. And yet all remain pertinent software development conversation. Bike
>> shed rainbows. You can make beautiful multicolored bike sheds with all of
>> them.
>>
>>
>> But discuss colors with someone else please. I can’t do it anymore.  But
>> I can discuss some jungle hack and slash momentum and trail blazing.  Give
>> me a moment. Time is fairly irrelevant on this dance floor. Tomorrow. Next
>> year. 3 years. Solr 42. It’s all the same timeline when the time comes.
>> Hell, my brain feels equally everywhere in all the timelines anyway. So one
>> moment, and I’ll point you to my speech, my journals, my old jungle dune
>> buggy - I did spend a moment or two once or twice preparing the damn thing
>> - just a moment or two, just 1, 2 or 3 times - and then the microphone is
>> all yours. But please, don’t talk to me about rainbows or shades of
>> magenta, I’m a jungle explorer, not a Sherwin Williams employee. Don’t
>> cover me with paint - I’m a roto spinning paint spewing machine. And I’d
>> love to spare you the paint ball war as well.
>>
>>
>> Links coming.
>>
>>
>> Mark
>>
>>
>>
>> --
>> - Mark
>>
>> http://about.me/markrmiller
>>
> --
- Mark

http://about.me/markrmiller

Reply via email to