Re: SolrCloud is sick.

> 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. >>>>&g

Re: SolrCloud is sick.

Figuring out a better overall algorithmic & data structure design that's an order of magnitude improvement seems far more important than swapping out libraries. And I say this as a Curator fan and committer. ;) On Mon, Nov 4, 2019 at 11:44 AM Erick Erickson wrote: > Bram: > > Using Curator has

Re: SolrCloud is sick.

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 toggled (DOWN and then UP!) every time a node restarts. Considering that we could just combine ACTIVE and `live_nodes` to understand whether a replica is available. It

[jira] [Commented] (SOLR-13320) add a param ignoreDuplicates=true to updates to not overwrite existing docs

[ https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826483#comment-16826483 ] Scott Blum commented on SOLR-13320: --- +1! > add a param ignoreDuplicates=

[jira] [Commented] (SOLR-13320) add a param ignoreDuplicates=true to updates to not overwrite existing docs

[ https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794015#comment-16794015 ] Scott Blum commented on SOLR-13320: --- Shalin lemme break this down a bit... Ima

[jira] [Comment Edited] (SOLR-13320) add a param ignoreDuplicates=true to updates to not overwrite existing docs

[ https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794015#comment-16794015 ] Scott Blum edited comment on SOLR-13320 at 3/15/19 11:1

[jira] [Comment Edited] (SOLR-13320) add a param ignoreDuplicates=true to updates to not overwrite existing docs

[ https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794015#comment-16794015 ] Scott Blum edited comment on SOLR-13320 at 3/15/19 11:1

[jira] [Resolved] (SOLR-5180) Core admin reload for an invalid core name returns 500 rather than 400 status code

[ https://issues.apache.org/jira/browse/SOLR-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved SOLR-5180. -- Resolution: Fixed This is now fixed > Core admin reload for an invalid core name returns 500 rat

[jira] [Assigned] (SOLR-5180) Core admin reload for an invalid core name returns 500 rather than 400 status code

[ https://issues.apache.org/jira/browse/SOLR-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned SOLR-5180: Assignee: Scott Blum > Core admin reload for an invalid core name returns 500 rather than

[jira] [Commented] (SOLR-8327) SolrDispatchFilter is not caching new state format, which results in live fetch from ZK per request if node does not contain core from collection

[ https://issues.apache.org/jira/browse/SOLR-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297371#comment-16297371 ] Scott Blum commented on SOLR-8327: -- https://github.com/apache/lucene-solr/pull

[jira] [Resolved] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved SOLR-11423. --- Resolution: Fixed Fix Version/s: master (8.0) 7.2 > Overseer queue need

[jira] [Comment Edited] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284021#comment-16284021 ] Scott Blum edited comment on SOLR-11423 at 12/8/17 6:5

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284021#comment-16284021 ] Scott Blum commented on SOLR-11423: --- I'm fixing solr/CHANGES.txt while cherr

[jira] [Comment Edited] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283972#comment-16283972 ] Scott Blum edited comment on SOLR-11423 at 12/8/17 6:2

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283972#comment-16283972 ] Scott Blum commented on SOLR-11423: --- Sounds good to me. > Overseer queue needs

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282711#comment-16282711 ] Scott Blum commented on SOLR-11423: --- I didn't resolve due to Noble's #co

Re: Welcome Noble Paul to the PMC

Congrats Noble! On Sun, Nov 19, 2017 at 3:02 PM, Adrien Grand wrote: > I am pleased to announce that Noble Paul has accepted the PMC's > invitation to join. > > Welcome Noble! >

[jira] [Commented] (SOLR-11590) Synchronize ZK connect/disconnect handling

[ https://issues.apache.org/jira/browse/SOLR-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238276#comment-16238276 ] Scott Blum commented on SOLR-11590: --- LGTM > Synchronize ZK connect/disconnect h

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236685#comment-16236685 ] Scott Blum commented on SOLR-11423: --- Oh wow, nice catch. How'd I mess th

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204874#comment-16204874 ] Scott Blum commented on SOLR-11423: --- Is it possible to pick a number related to

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204443#comment-16204443 ] Scott Blum commented on SOLR-11443: --- LGTM > Remove the usage of workqueue for O

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204004#comment-16204004 ] Scott Blum commented on SOLR-11423: --- I'm happy to defer on this issue, but I

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204001#comment-16204001 ] Scott Blum commented on SOLR-11443: --- SOLR-11447 looks interesting, might well add

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203992#comment-16203992 ] Scott Blum commented on SOLR-11443: --- BTW, have you tried out github PRs? It woul

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201129#comment-16201129 ] Scott Blum commented on SOLR-11443: --- Should probably deprecate and update all the

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201095#comment-16201095 ] Scott Blum commented on SOLR-11443: --- Can you talk me through: {code}

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201120#comment-16201120 ] Scott Blum commented on SOLR-11443: --- Just a few nits / questions, otherwise

[jira] [Comment Edited] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201107#comment-16201107 ] Scott Blum edited comment on SOLR-11443 at 10/11/17 10:4

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201107#comment-16201107 ] Scott Blum commented on SOLR-11443: --- it might be more clear to do

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201081#comment-16201081 ] Scott Blum commented on SOLR-11443: --- When would numUpdates diverge from updates.

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201074#comment-16201074 ] Scott Blum commented on SOLR-11443: --- I feel like the maybeFlushBefore, maybeFlushA

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201064#comment-16201064 ] Scott Blum commented on SOLR-11443: --- I might be thinking about this wrong, but the

[jira] [Commented] (SOLR-11443) Remove the usage of workqueue for Overseer

[ https://issues.apache.org/jira/browse/SOLR-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200881#comment-16200881 ] Scott Blum commented on SOLR-11443: --- Love the idea; having a separate queue-work n

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194900#comment-16194900 ] Scott Blum commented on SOLR-11423: --- Perhaps you're right. In our clust

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193435#comment-16193435 ] Scott Blum commented on SOLR-11423: --- [~noble.paul] both good questions! > Thi

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191962#comment-16191962 ] Scott Blum commented on SOLR-11423: --- [~shalinmangar] [~noble.paul] either of you

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1617#comment-1617 ] Scott Blum commented on SOLR-11423: --- Patch passes tests for me. > Overseer queu

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188867#comment-16188867 ] Scott Blum commented on SOLR-11423: --- [~noble.paul] I went with 20k. We could mak

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188803#comment-16188803 ] Scott Blum commented on SOLR-11423: --- [~erickerickson] I have backported change

[jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

[ https://issues.apache.org/jira/browse/SOLR-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186282#comment-16186282 ] Scott Blum commented on SOLR-11423: --- CC: [~jhump] [~noble.paul] [~shalinma

[jira] [Created] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect

Scott Blum created SOLR-11423: - Summary: Overseer queue needs a hard cap (maximum size) that clients respect Key: SOLR-11423 URL: https://issues.apache.org/jira/browse/SOLR-11423 Project: Solr

[jira] [Commented] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078603#comment-16078603 ] Scott Blum commented on SOLR-11025: --- Thanks guys! I didn't bother adding an

[jira] [Assigned] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned SOLR-11025: - Assignee: Scott Blum > OverseerTest.testShardLeaderChange() failu

[jira] [Resolved] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved SOLR-11025. --- Resolution: Fixed > OverseerTest.testShardLeaderChange() failu

[jira] [Commented] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078506#comment-16078506 ] Scott Blum commented on SOLR-11025: --- You da bomb [~steve_

[jira] [Commented] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078440#comment-16078440 ] Scott Blum commented on SOLR-11025: --- Will committing to master be sufficient a

[jira] [Updated] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-11025: -- Attachment: SOLR-11025.patch Any way to test if this fixes the failure before we commit it to 3

[jira] [Commented] (SOLR-11025) OverseerTest.testShardLeaderChange() failures

[ https://issues.apache.org/jira/browse/SOLR-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077749#comment-16077749 ] Scott Blum commented on SOLR-11025: --- Possible issue: the order or operations in

[jira] [Commented] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

[ https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075666#comment-16075666 ] Scott Blum commented on SOLR-10983: --- BTW: this issue most likely affects all

[jira] [Resolved] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

[ https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved SOLR-10983. --- Resolution: Fixed Fix Version/s: 7.1 master (8.0) 7.0

[jira] [Commented] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

[ https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074225#comment-16074225 ] Scott Blum commented on SOLR-10983: --- Thanks! Will do > Fix DOWNNODE ->

[jira] [Commented] (SOLR-10276) Update ZK leader election so that leader notices if its leadership is revoked

[ https://issues.apache.org/jira/browse/SOLR-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070340#comment-16070340 ] Scott Blum commented on SOLR-10276: --- Please add a patch! This is super us

[jira] [Assigned] (SOLR-10276) Update ZK leader election so that leader notices if its leadership is revoked

[ https://issues.apache.org/jira/browse/SOLR-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned SOLR-10276: - Assignee: Scott Blum > Update ZK leader election so that leader notices if its leadership

[jira] [Commented] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

[ https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069503#comment-16069503 ] Scott Blum commented on SOLR-10983: --- [~shalinmangar] [~jhump] > Fix DOWNNODE -

[jira] [Updated] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

[ https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10983: -- Attachment: SOLR-10983.patch > Fix DOWNNODE -> queue-work exp

[jira] [Created] (SOLR-10983) Fix DOWNNODE -> queue-work explosion

Scott Blum created SOLR-10983: - Summary: Fix DOWNNODE -> queue-work explosion Key: SOLR-10983 URL: https://issues.apache.org/jira/browse/SOLR-10983 Project: Solr Issue Type: Bug Secur

Re: Am I'm missing something obvious about subfacets?

Thanks, Yonik! Glad to hear I'm not completely crazy. We should probably update to 6.x and try out streaming. On Sat, May 20, 2017 at 7:13 AM, Yonik Seeley wrote: > On Fri, May 19, 2017 at 6:36 PM, Scott Blum wrote: > > Hi folks, > > > > I think I'm missing

Am I'm missing something obvious about subfacets?

Hi folks, I think I'm missing something fundamental about how subfacets work and relate to each other. I don't really understand when it's legal to reference a subfacet, and when it's not. For example, here's a simple subfacet example from http://yonik.com/solr-subfacets/ top_authors:{

Re: update request parameter to quietly drop conflicts

Oh nice! Didn't realize that's there in 6x (I'm on 5.5.3). Thanks!! On Wed, May 17, 2017 at 12:40 AM, David Smiley wrote: > SkipExistingDocumentsProcessorFactory >

update request parameter to quietly drop conflicts

Hi folks, Recently ran into a data merge use case where I want to backfill a ton of documents off of storage into solr, but only if they don't already exist in Solr. (If they exist, they're newer.) I couldn't find an efficient way to do this in bulk; if any document in my batch ran into a confli

[jira] [Updated] (SOLR-10619) Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10619: -- Attachment: SOLR-10619-dragonsinth.patch What do you think about this? > Optimize using cache

[jira] [Commented] (SOLR-10619) Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002053#comment-16002053 ] Scott Blum commented on SOLR-10619: --- [~caomanhdat] Okay, I see what's goin

[jira] [Commented] (SOLR-10619) Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002013#comment-16002013 ] Scott Blum commented on SOLR-10619: --- Hmm lemme take a look. Maybe that test sh

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001872#comment-16001872 ] Scott Blum commented on SOLR-10619: --- [~caomanhdat] patch LGTM. I would update the

[jira] [Commented] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001856#comment-16001856 ] Scott Blum commented on SOLR-10524: --- Thanks [~caomanhdat], committed to ma

[jira] [Updated] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10524: -- Summary: Better ZkStateWriter batching (was: Explore in-memory partitioning for processing Overseer

[jira] [Updated] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10524: -- Attachment: SOLR-10524-dragonsinth.patch Fixes ZkStateWriterTest, etc > Explore in-memory partition

[jira] [Commented] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001810#comment-16001810 ] Scott Blum commented on SOLR-10524: --- ZkStateWriterTests.testZkStateWriterBatching(

Re: Welcome Mike Drob as Lucene/Solr committer

Congrats, Mike! On Mon, May 8, 2017 at 1:25 PM, Erick Erickson wrote: > Welcome Mike! > > On Mon, May 8, 2017 at 10:15 AM, Mike Drob wrote: > > Thanks, Mark. > > > > My first experience with Solr was through working on a custom indexer, > but > > since then I've seen more and more of the intern

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000304#comment-16000304 ] Scott Blum commented on SOLR-10619: --- I'll take another look tomorrow

[jira] [Commented] (SOLR-10285) Reduce state messages when there are leader only shards

[ https://issues.apache.org/jira/browse/SOLR-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000303#comment-16000303 ] Scott Blum commented on SOLR-10285: --- [~jhump] did you have a patch for this? or di

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999680#comment-15999680 ] Scott Blum commented on SOLR-10619: --- Sounds good! > When DQ.knowChildren is no

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999652#comment-15999652 ] Scott Blum commented on SOLR-10619: --- Good thought. I was debating the same thing i

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999586#comment-15999586 ] Scott Blum commented on SOLR-10619: --- I completely follow your logic. But then, wh

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999299#comment-15999299 ] Scott Blum commented on SOLR-10619: --- What's the whole "singleConsumer&qu

[jira] [Commented] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997804#comment-15997804 ] Scott Blum commented on SOLR-10524: --- Updated patch DistributedQueue LGTM > Exp

[jira] [Commented] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997500#comment-15997500 ] Scott Blum commented on SOLR-10524: --- Couple of thoughts: 1) In the places where yo

[jira] [Comment Edited] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997500#comment-15997500 ] Scott Blum edited comment on SOLR-10524 at 5/4/17 9:5

[jira] [Resolved] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved SOLR-10420. --- Resolution: Fixed > Solr 6.x leaking one SolrZkClient instance per sec

Re: [VOTE] Release Lucene/Solr 6.5.1 RC1

Commit e3beb61a72efbce37710ce3cc48b24093070d052 in lucene-solr's branch refs/heads/branch_6_5 from Scott Blum <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dragonsinth> [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e3beb61 ] SOLR-10420 <https://iss

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973346#comment-15973346 ] Scott Blum commented on SOLR-10420: --- Got it. I do think it would be a mistake.

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Fix Version/s: (was: 6.4.3) > Solr 6.x leaking one SolrZkClient instance per sec

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Fix Version/s: 5.6 > Solr 6.x leaking one SolrZkClient instance per sec

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973320#comment-15973320 ] Scott Blum commented on SOLR-10420: --- So my plan is to commit this to master, branc

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Fix Version/s: 6.6 > Solr 6.x leaking one SolrZkClient instance per sec

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Fix Version/s: master (7.0) 6.5.1 6.4.3 5.5.5

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973246#comment-15973246 ] Scott Blum commented on SOLR-10420: --- Great! Thanks [~steve_rowe]! I'll

[jira] [Comment Edited] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973093#comment-15973093 ] Scott Blum edited comment on SOLR-10420 at 4/18/17 5:1

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973093#comment-15973093 ] Scott Blum commented on SOLR-10420: --- Agreed. It passes for me. Anyone on this i

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Attachment: (was: SOLR-10420-dragonsinth.patch) > Solr 6.x leaking one SolrZkClient instance

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Attachment: SOLR-10420-dragonsinth.patch > Solr 6.x leaking one SolrZkClient instance per sec

[jira] [Assigned] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned SOLR-10420: - Assignee: Scott Blum > Solr 6.x leaking one SolrZkClient instance per sec

[jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated SOLR-10420: -- Attachment: SOLR-10420-dragonsinth.patch [~caomanhdat] [~jhump] I think this may be the right approach

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971259#comment-15971259 ] Scott Blum commented on SOLR-10420: --- [~caomanhdat] I didn't literally mea

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970030#comment-15970030 ] Scott Blum commented on SOLR-10420: --- Let me try to unpack what you said.. 1) We wa

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968618#comment-15968618 ] Scott Blum commented on SOLR-10420: --- Fix LGTM. Is this actual fix

[jira] [Commented] (SOLR-10277) On 'downnode', lots of wasteful mutations are done to ZK

[ https://issues.apache.org/jira/browse/SOLR-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957285#comment-15957285 ] Scott Blum commented on SOLR-10277: --- Thank you Shalin! > On 'downno

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955283#comment-15955283 ] Scott Blum commented on SOLR-10420: --- Hard to see how the problem could be localize

[jira] [Commented] (SOLR-10277) On 'downnode', lots of wasteful mutations are done to ZK

[ https://issues.apache.org/jira/browse/SOLR-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955274#comment-15955274 ] Scott Blum commented on SOLR-10277: --- Agreed, [~shalinmangar] I'm actually OOO

[jira] [Commented] (SOLR-10277) On 'downnode', lots of wasteful mutations are done to ZK

[ https://issues.apache.org/jira/browse/SOLR-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948316#comment-15948316 ] Scott Blum commented on SOLR-10277: --- Sure thing, no rush! Would love to get more

  1   2   3   4   5   6   >