Re: SolrCloud is sick.

Sorry you guys got to play therapist for a bit. 10 years to get over, most of it buried. Had to let that beast out. On Wed, Nov 6, 2019 at 12:33 AM Mark Miller wrote: > Another Overseer :) > > I don't mean to contradict your curator statement either - I talk with the > authority of god but with

Re: SolrCloud is sick.

Another Overseer :) I don't mean to contradict your curator statement either - I talk with the authority of god but with the confidence of no one ;) On Tue, Nov 5, 2019 at 7:44 PM Scott Blum wrote: > WHO OVERSEES THE OVERSEER > > On Tue, Nov 5, 2019 at 5:16 PM Mark Miller wrote: > >> bq.

Re: [VOTE] Release Lucene/Solr 8.3.0 RC2

It seems that the Lucene 8.3.0 release announcement hasn't made its way to the asf-announce mailing list. I cannot find it in the archives but I see the solr one there. On Mon, Nov 4, 2019 at 1:06 AM Jan Høydahl wrote: > In my opinion it would have been better to delay the release announcement

Re: SolrCloud is sick.

WHO OVERSEES THE OVERSEER On Tue, Nov 5, 2019 at 5:16 PM Mark Miller wrote: > bq. SolrCloud is a ballerina. Doesn't look it, cause we dont take care > of it. > > And this is why I'm so devastated by the Overseer. I don't blame anyone > person. Where was the manual, where was my

Questions about corrupted Segments files.

Hello, Community members: I am using Solr 7.7.2. On the other day, while indexing to the Solr, my computer powered off. As a result, there are corrupted segment files. Is there any way to fix the corrupted segment files without re-indexing? I have read a blog post (in Japanese) writing about

Re: SolrCloud is sick.

Bottom line, garden is a fricken mess and there are tons of attempts to solve shit the wrong way cause nobody understands what was intended here. At least one of those is on me. Mark On Tue, Nov 5, 2019 at 10:16 PM Mark Miller wrote: > bq. SolrCloud is a ballerina. Doesn't look it, cause we

Re: SolrCloud is sick.

bq. SolrCloud is a ballerina. Doesn't look it, cause we dont take care of it. And this is why I'm so devastated by the Overseer. I don't blame anyone person. Where was the manual, where was my intervention. I whispered Overseer and cut one more thing off my list of responsibilities. But the

Re: [ANNOUNCE] Apache Solr 8.3.0 released

Hey Cassandra, Thank you for prompt response. I look forward to contribute to Solr Documentation . Really love the community! ^_^ PS: We need to fix the Public Servers Listing section on homepage

Re: SolrCloud is sick.

And now we are to meat of it. Fill in here: https://issues.apache.org/jira/browse/SOLR-13888 We can play in a better world, we can have fun, but some of you are going to have to adjust your ways. In the most convenient way possible. You are all great people, I don't want to cause you annoyance,

Re: SolrCloud is sick.

If you had any idea how much suffering just that has caused. Not just users, but us. Mark On Tue, Nov 5, 2019 at 10:38 AM Mark Miller wrote: > It’s like 6-7 years since I quickly added a shitty collections API in my > free time because we desperately needed SOMETHING. I don’t know if I tried >

Re: SolrCloud is sick.

It’s like 6-7 years since I quickly added a shitty collections API in my free time because we desperately needed SOMETHING. I don’t know if I tried to make it wait for proper state or what , it was a stub to try get things moving. That call, to this day, along with all our other checks, until some

Re: SolrCloud is sick.

I'll tell you what guys, development right now sucks. I don't enjoy. But when I start to put things in shape? I get this smile, and I start going with the feeling of I don't need you guys, I don't users, I don't need a job, cause just this is figgen nice. On Tue, Nov 5, 2019 at 9:59 AM Mark

Re: SolrCloud is sick.

I suppose I should toss one more out. Hell yes, we will be using curator. It's insane for any group larger than 2-3 to directly use ZooKeeper. Even for that group, you want some damn good reasons to not use curator. We can start using more assembly too (joke Yonik). Curator was an option

Re: SolrCloud is sick.

And look, we started pretty deep in the hole. Solr started with tons of bug or limitations that hardly mattered to it and hit SolrCloud in the eye like a train. And we were not setup to deal with that. We never had a nice garden for SolrCloud. We started in a mess, thinking, eventually we clear

Re: [ANNOUNCE] Apache Solr 8.3.0 released

We’re still working out the changes to the publication process, and got a couple wires crossed that prevented the Ref Guide from being published at the same time for this release. I’ve published the final version now: http://lucene.apache.org/solr/guide/8_3/. Apologies for the confusion, by

Re: SolrCloud is sick.

Basically I can fix 99% of this without you guys - with simple care and effort and time that non of you are likely in the circumstances of being able to duplicate.. Been there done that, made it 100x-1000x faster to boot and added all kinds of fun. But I can't build the rest of Solr. I don't care

Re: dtd anomaly

if i delete the invalid host DTD ENTITY_TermQuery.xml from xslt input folder everything works thanks uwe From: Uwe Schindler Sent: Monday, November 4, 2019 8:04 AM To: dev@lucene.apache.org Subject: Re: dtd anomaly This job is ran on every ant build on Jenkins

Re: SolrCloud is sick.

There are 10,000 problems here. So if you eventually land on one possible solution you agree on, we a little closer. There is no problem with the current design. Design's can always be improved, sure. I've made this one fast. You won't believe me fast. The low hanging fruit is astronomical,