[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch Another patch, integrates the patch for SOLR-6075. Will remove this befo

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch Patch that makes a few vars final (tracking related). Also, completedTas

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1311#comment-1311 ] Anshum Gupta commented on SOLR-5681: I would like to move ahead with committing this pa

[jira] [Comment Edited] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999323#comment-13999323 ] Anshum Gupta edited comment on SOLR-5681 at 5/15/14 10:55 PM: --

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch Patch that addresses all of the things you had recommended. Here's a sum

[jira] [Commented] (SOLR-6075) CoreAdminHandler should synchronize while adding a task to the tracking map

[ https://issues.apache.org/jira/browse/SOLR-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999464#comment-13999464 ] Anshum Gupta commented on SOLR-6075: The addTask(String map, TaskObject o, boolean limi

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch Made 'stale' in OCP a local variable and documented the use of the varia

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch bq. This patch still has the new createCollection method in CollectionA

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch A patch with fix for a potential NPE in a log.debug message. > Make the

[jira] [Comment Edited] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002109#comment-14002109 ] Anshum Gupta edited comment on SOLR-5681 at 5/19/14 6:17 PM: - A

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Attachment: SOLR-5681-2.patch A patch that handles all of that. I'm running the tests and the precommi

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003518#comment-14003518 ] Anshum Gupta commented on SOLR-5681: I had created SOLR-5886 for that. Will take that o

[jira] [Commented] (SOLR-5886) Propagate more information in case of failed async tasks

[ https://issues.apache.org/jira/browse/SOLR-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003579#comment-14003579 ] Anshum Gupta commented on SOLR-5886: sure, makes sense. > Propagate more information i

[jira] [Commented] (SOLR-5495) Recovery strategy for leader partitioned from replica case.

[ https://issues.apache.org/jira/browse/SOLR-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003626#comment-14003626 ] Anshum Gupta commented on SOLR-5495: The CHANGES.txt entry for trunk and 4x are in diff

[jira] [Resolved] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5681. Resolution: Fixed > Make the OverseerCollectionProcessor multi-threaded > --

[jira] [Created] (SOLR-6099) Fix cleanup mechanism for a previous (failed) SPLITSHARD

Anshum Gupta created SOLR-6099: -- Summary: Fix cleanup mechanism for a previous (failed) SPLITSHARD Key: SOLR-6099 URL: https://issues.apache.org/jira/browse/SOLR-6099 Project: Solr Issue Type: B

[jira] [Resolved] (SOLR-5892) Document asynchronous OCP and CoreAdmin calls

[ https://issues.apache.org/jira/browse/SOLR-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5892. Resolution: Fixed Fix Version/s: 4.8 > Document asynchronous OCP and CoreAdmin calls > --

[jira] [Updated] (SOLR-6041) Collection API REQUESTSTATUS call should support multiple requestids

[ https://issues.apache.org/jira/browse/SOLR-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6041: --- Summary: Collection API REQUESTSTATUS call should support multiple requestids (was: Collection API RE

[jira] [Commented] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007767#comment-14007767 ] Anshum Gupta commented on SOLR-6026: Yes. Though I should be able to get to it by the w

[jira] [Commented] (SOLR-6112) TestRequestStatusCollectionAPI failures on jenkins

[ https://issues.apache.org/jira/browse/SOLR-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008285#comment-14008285 ] Anshum Gupta commented on SOLR-6112: Thanks for taking this up Shalin. This should fix

[jira] [Created] (SOLR-6122) API to cancel an already submitted/running Collections API call

Anshum Gupta created SOLR-6122: -- Summary: API to cancel an already submitted/running Collections API call Key: SOLR-6122 URL: https://issues.apache.org/jira/browse/SOLR-6122 Project: Solr Issue

[jira] [Updated] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6026: --- Attachment: SOLR-6026.patch This might not be the most efficient way to implement it but I think this

[jira] [Updated] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6026: --- Attachment: SOLR-6026.patch Some fixes to the tests. > Also check work-queue while processing a REQUE

[jira] [Resolved] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-6026. Resolution: Fixed > Also check work-queue while processing a REQUESTSTATUS Collection API Call > ---

[jira] [Updated] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6026: --- Fix Version/s: (was: 4.8.1) 4.9 > Also check work-queue while processing a REQU

[jira] [Assigned] (SOLR-6026) Also check work-queue while processing a REQUESTSTATUS Collection API Call

[ https://issues.apache.org/jira/browse/SOLR-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-6026: -- Assignee: Anshum Gupta > Also check work-queue while processing a REQUESTSTATUS Collection API C

[jira] [Updated] (SOLR-5886) Store the response in zk for async calls so that it can be returned by REQUESTSTATUS API

[ https://issues.apache.org/jira/browse/SOLR-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5886: --- Summary: Store the response in zk for async calls so that it can be returned by REQUESTSTATUS API (wa

[jira] [Updated] (SOLR-5886) Store the response in zk for async calls so that it can be returned by REQUESTSTATUS API

[ https://issues.apache.org/jira/browse/SOLR-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5886: --- Attachment: SOLR-5886.patch Patch that saves the information in zk. I'm trying to figure a sensible st

[jira] [Updated] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6123: --- Attachment: SOLR-6123.patch Fix with a test. > The 'clusterstatus' API filtered by collection times o

[jira] [Assigned] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-6123: -- Assignee: Anshum Gupta > The 'clusterstatus' API filtered by collection times out if a long runn

[jira] [Updated] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6123: --- Attachment: SOLR-6123.patch Updated patch. > The 'clusterstatus' API filtered by collection times out

[jira] [Resolved] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-6123. Resolution: Fixed > The 'clusterstatus' API filtered by collection times out if a long running > op

[jira] [Created] (SOLR-6148) Failure on Jenkins: leaked parallelCoreAdminExecutor threads

Anshum Gupta created SOLR-6148: -- Summary: Failure on Jenkins: leaked parallelCoreAdminExecutor threads Key: SOLR-6148 URL: https://issues.apache.org/jira/browse/SOLR-6148 Project: Solr Issue Ty

[jira] [Updated] (SOLR-6148) Failure on Jenkins: leaked parallelCoreAdminExecutor threads

[ https://issues.apache.org/jira/browse/SOLR-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6148: --- Attachment: SOLR-6148.patch The parallelExecutor in CoreAdminHandler is no longer lazy init'ed as it

[jira] [Commented] (SOLR-6148) Failure on Jenkins: leaked parallelCoreAdminExecutor threads

[ https://issues.apache.org/jira/browse/SOLR-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020582#comment-14020582 ] Anshum Gupta commented on SOLR-6148: Leaving this open for a day. If there are no more

[jira] [Resolved] (SOLR-6148) Failure on Jenkins: leaked parallelCoreAdminExecutor threads

[ https://issues.apache.org/jira/browse/SOLR-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-6148. Resolution: Fixed > Failure on Jenkins: leaked parallelCoreAdminExecutor threads > -

[jira] [Commented] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026022#comment-14026022 ] Anshum Gupta commented on SOLR-6123: There were 2 calls during the Split shard and that

[jira] [Commented] (SOLR-6123) The 'clusterstatus' API filtered by collection times out if a long running operation is in progress

[ https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026133#comment-14026133 ] Anshum Gupta commented on SOLR-6123: Allowing both would actually not even be a test. I

[jira] [Commented] (SOLR-6095) SolrCloud cluster can end up without an overseer

[ https://issues.apache.org/jira/browse/SOLR-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033451#comment-14033451 ] Anshum Gupta commented on SOLR-6095: RollingRestartTest.regularRestartTest() is comment

[jira] [Updated] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5477: --- Attachment: SOLR-5477.patch Patch with SolrJ support and tests. > Async execution of OverseerCollecti

[jira] [Commented] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936061#comment-13936061 ] Anshum Gupta commented on SOLR-5477: Thanks for pointing that out Steve. This must have

[jira] [Updated] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5477: --- Attachment: SOLR-5477.urlschemefix.patch Fix for not modifying url scheme. > Async execution of Overs

[jira] [Resolved] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5477. Resolution: Fixed Fix Version/s: 4.8 > Async execution of OverseerCollectionProcessor tasks >

[jira] [Updated] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5477: --- Fix Version/s: 5.0 > Async execution of OverseerCollectionProcessor tasks > --

[jira] [Updated] (SOLR-5876) createCollection(String name, String shards, Integer repl, Integer maxShards, String conf, String routerField, SolrServer server) appears to call itself.

[ https://issues.apache.org/jira/browse/SOLR-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5876: --- Attachment: SOLR-5876.patch Patch with some extra cleanup of imports in a related test. > createColle

[jira] [Resolved] (SOLR-5876) createCollection(String name, String shards, Integer repl, Integer maxShards, String conf, String routerField, SolrServer server) appears to call itself.

[ https://issues.apache.org/jira/browse/SOLR-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5876. Resolution: Fixed > createCollection(String name, String shards, Integer repl, Integer > maxShards

[jira] [Created] (SOLR-5886) Propagate more information in case of failed async tasks

Anshum Gupta created SOLR-5886: -- Summary: Propagate more information in case of failed async tasks Key: SOLR-5886 URL: https://issues.apache.org/jira/browse/SOLR-5886 Project: Solr Issue Type: I

[jira] [Created] (SOLR-5892) Document asynchronous OCP and CoreAdmin calls

Anshum Gupta created SOLR-5892: -- Summary: Document asynchronous OCP and CoreAdmin calls Key: SOLR-5892 URL: https://issues.apache.org/jira/browse/SOLR-5892 Project: Solr Issue Type: Task

[jira] [Created] (SOLR-5908) Make REQUESTSTATUS call non-blocking and non-blocked

Anshum Gupta created SOLR-5908: -- Summary: Make REQUESTSTATUS call non-blocking and non-blocked Key: SOLR-5908 URL: https://issues.apache.org/jira/browse/SOLR-5908 Project: Solr Issue Type: Impro

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949465#comment-13949465 ] Anshum Gupta commented on SOLR-5473: Adding to that, testing this for ASYNC calls would

[jira] [Commented] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949485#comment-13949485 ] Anshum Gupta commented on SOLR-5477: [~noble.paul] This one doesn't really belong to th

[jira] [Commented] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks

[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949524#comment-13949524 ] Anshum Gupta commented on SOLR-5477: [~noble.paul] for now it's more of a string. SOLR-

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950067#comment-13950067 ] Anshum Gupta commented on SOLR-5473: Can you also remove the redundant typing (diamond

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951642#comment-13951642 ] Anshum Gupta commented on SOLR-5473: More comments: # Removing the commented out code

[jira] [Updated] (SOLR-5908) Make REQUESTSTATUS call non-blocking and non-blocked

[ https://issues.apache.org/jira/browse/SOLR-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5908: --- Attachment: SOLR-5908.patch Patch that makes the REQUESTSTATUS Collection API call non-blocking and n

[jira] [Updated] (SOLR-5908) Make REQUESTSTATUS call non-blocking and non-blocked

[ https://issues.apache.org/jira/browse/SOLR-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5908: --- Attachment: SOLR-5908.patch Updated patch with a quick test. Updated the AsyncMigrateRouteKeyTest to c

[jira] [Resolved] (SOLR-5908) Make REQUESTSTATUS call non-blocking and non-blocked

[ https://issues.apache.org/jira/browse/SOLR-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5908. Resolution: Fixed Fix Version/s: 5.0 4.8 Committed into trunk and branch_4

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959383#comment-13959383 ] Anshum Gupta commented on SOLR-5681: Here's another approach: Follow approach#2 with th

[jira] [Assigned] (SOLR-5957) Note on -numShards obsolete in ref guide

[ https://issues.apache.org/jira/browse/SOLR-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-5957: -- Assignee: Anshum Gupta > Note on -numShards obsolete in ref guide >

[jira] [Resolved] (SOLR-5957) Note on -numShards obsolete in ref guide

[ https://issues.apache.org/jira/browse/SOLR-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-5957. Resolution: Fixed Fix Version/s: 5.0 4.8 Fixed in the ref guide. > Note o

[jira] [Assigned] (SOLR-5958) Document (and fix) numShards and router selection parameter in SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-5958: -- Assignee: Anshum Gupta > Document (and fix) numShards and router selection parameter in SolrClou

[jira] [Created] (SOLR-5958) Document (and fix) numShards and router selection parameter in SolrCloud

Anshum Gupta created SOLR-5958: -- Summary: Document (and fix) numShards and router selection parameter in SolrCloud Key: SOLR-5958 URL: https://issues.apache.org/jira/browse/SOLR-5958 Project: Solr

[jira] [Commented] (SOLR-5957) Note on -numShards obsolete in ref guide

[ https://issues.apache.org/jira/browse/SOLR-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960191#comment-13960191 ] Anshum Gupta commented on SOLR-5957: Thanks for mentioning that [~markrmil...@gmail.com

[jira] [Commented] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964796#comment-13964796 ] Anshum Gupta commented on SOLR-5681: It's supposed to work in the following cases: * Ca

[jira] [Commented] (LUCENE-5590) remove .zip binary artifacts

[ https://issues.apache.org/jira/browse/LUCENE-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965956#comment-13965956 ] Anshum Gupta commented on LUCENE-5590: -- I think [~upayavira] is referring to trainin

[jira] [Commented] (SOLR-5986) Don't allow runaway queries from harming Solr cluster health or search performance

[ https://issues.apache.org/jira/browse/SOLR-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061722#comment-14061722 ] Anshum Gupta commented on SOLR-5986: I was trying to look at this. As far as I see, the

[jira] [Created] (SOLR-6248) MoreLikeThis Query Parser

Anshum Gupta created SOLR-6248: -- Summary: MoreLikeThis Query Parser Key: SOLR-6248 URL: https://issues.apache.org/jira/browse/SOLR-6248 Project: Solr Issue Type: New Feature Reporter

[jira] [Commented] (SOLR-5480) Make MoreLikeThisHandler distributable

[ https://issues.apache.org/jira/browse/SOLR-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062358#comment-14062358 ] Anshum Gupta commented on SOLR-5480: [~vzhovtiuk] This is very different from what this

[jira] [Commented] (SOLR-6257) More than two "!"-s in a doc ID throws an ArrayIndexOutOfBoundsException when using the composite id router

[ https://issues.apache.org/jira/browse/SOLR-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066937#comment-14066937 ] Anshum Gupta commented on SOLR-6257: This looks good to me. The only suggestion is to m

[jira] [Commented] (SOLR-6257) More than two "!"-s in a doc ID throws an ArrayIndexOutOfBoundsException when using the composite id router

[ https://issues.apache.org/jira/browse/SOLR-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067471#comment-14067471 ] Anshum Gupta commented on SOLR-6257: +1. LGTM! > More than two "!"-s in a doc ID throw

[jira] [Commented] (SOLR-4999) Make the collections API consistent by using 'collection' instead of 'name'

[ https://issues.apache.org/jira/browse/SOLR-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067621#comment-14067621 ] Anshum Gupta commented on SOLR-4999: Thinking about all the APIs, the name/collection s

[jira] [Commented] (SOLR-6248) MoreLikeThis Query Parser

[ https://issues.apache.org/jira/browse/SOLR-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070897#comment-14070897 ] Anshum Gupta commented on SOLR-6248: What do you mean by "text that isn't in the index"

[jira] [Commented] (SOLR-6248) MoreLikeThis Query Parser

[ https://issues.apache.org/jira/browse/SOLR-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071753#comment-14071753 ] Anshum Gupta commented on SOLR-6248: I don't think this would really work across 2 coll

[jira] [Commented] (SOLR-6248) MoreLikeThis Query Parser

[ https://issues.apache.org/jira/browse/SOLR-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074514#comment-14074514 ] Anshum Gupta commented on SOLR-6248: My bad, this was my mistake. The last time I'd loo

[jira] [Updated] (SOLR-5681) Make the OverseerCollectionProcessor multi-threaded

[ https://issues.apache.org/jira/browse/SOLR-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5681: --- Fix Version/s: 4.9 5.0 > Make the OverseerCollectionProcessor multi-threaded >

[jira] [Commented] (SOLR-5986) Don't allow runaway queries from harming Solr cluster health or search performance

[ https://issues.apache.org/jira/browse/SOLR-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079976#comment-14079976 ] Anshum Gupta commented on SOLR-5986: I'm trying to solve this problem a little differen

[jira] [Commented] (SOLR-5986) Don't allow runaway queries from harming Solr cluster health or search performance

[ https://issues.apache.org/jira/browse/SOLR-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081369#comment-14081369 ] Anshum Gupta commented on SOLR-5986: You're right Steve. Also, I tried something that I

[jira] [Updated] (SOLR-5986) Don't allow runaway queries from harming Solr cluster health or search performance

[ https://issues.apache.org/jira/browse/SOLR-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-5986: --- Attachment: SOLR-5986.patch Working on adding more test and to decide on where the ExitableReader actu

[jira] [Updated] (SOLR-6249) Schema API changes return success before all cores are updated

[ https://issues.apache.org/jira/browse/SOLR-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6249: --- Summary: Schema API changes return success before all cores are updated (was: from ) > Schema API c

[jira] [Updated] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6379: --- Summary: new replicas seem to be involved in queries before they are ready (was: new replicas seem to

[jira] [Assigned] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta reassigned SOLR-6379: -- Assignee: Anshum Gupta > new replicas seem to be involved in queries before they are ready > ---

[jira] [Commented] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101033#comment-14101033 ] Anshum Gupta commented on SOLR-6379: This seems like something that should go into 4.10

[jira] [Commented] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101139#comment-14101139 ] Anshum Gupta commented on SOLR-6379: [~markrmil...@gmail.com] right, seems like it's ri

[jira] [Comment Edited] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101139#comment-14101139 ] Anshum Gupta edited comment on SOLR-6379 at 8/18/14 7:32 PM: - [

[jira] [Commented] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101240#comment-14101240 ] Anshum Gupta commented on SOLR-6379: I think it would make sense to consider zkawarenes

[jira] [Commented] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101315#comment-14101315 ] Anshum Gupta commented on SOLR-6379: bq. Perhaps we just have to favor collection over

[jira] [Commented] (SOLR-5380) Using cloudSolrServer.setDefaultCollection(collectionId) does not work as intended for an alias spanning more than 1 collection.

[ https://issues.apache.org/jira/browse/SOLR-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101346#comment-14101346 ] Anshum Gupta commented on SOLR-5380: [~markrmil...@gmail.com] Is this already fixed? >

[jira] [Commented] (SOLR-6379) new replicas seem to be involved in queries before they are ready

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101356#comment-14101356 ] Anshum Gupta commented on SOLR-6379: bq. If you resolve the collection first, it can be

[jira] [Created] (SOLR-6391) Improve message for CREATECOLLECTION failure due to missing numShards

Anshum Gupta created SOLR-6391: -- Summary: Improve message for CREATECOLLECTION failure due to missing numShards Key: SOLR-6391 URL: https://issues.apache.org/jira/browse/SOLR-6391 Project: Solr

[jira] [Commented] (SOLR-6379) CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102413#comment-14102413 ] Anshum Gupta commented on SOLR-6379: [~markrmil...@gmail.com] That's ok :). I'll put up

[jira] [Updated] (SOLR-6379) CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6379: --- Attachment: SOLR-6379.patch Simpler test that doesn't involve any of the pivot faceting stuff. Added a

[jira] [Updated] (SOLR-6379) CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6379: --- Attachment: SOLR-6379.patch Added a test but it's failing. Looking at what's missing/wrong. CloudSolrS

[jira] [Updated] (SOLR-6391) Improve message for CREATECOLLECTION failure due to missing numShards

[ https://issues.apache.org/jira/browse/SOLR-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6391: --- Priority: Minor (was: Major) > Improve message for CREATECOLLECTION failure due to missing numShards

[jira] [Updated] (SOLR-6391) Improve message for CREATECOLLECTION failure due to missing numShards

[ https://issues.apache.org/jira/browse/SOLR-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6391: --- Attachment: SOLR-6391.patch > Improve message for CREATECOLLECTION failure due to missing numShards >

[jira] [Updated] (SOLR-6391) Improve message for CREATECOLLECTION failure due to missing numShards

[ https://issues.apache.org/jira/browse/SOLR-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6391: --- Affects Version/s: 4.9 > Improve message for CREATECOLLECTION failure due to missing numShards > -

[jira] [Resolved] (SOLR-6391) Improve message for CREATECOLLECTION failure due to missing numShards

[ https://issues.apache.org/jira/browse/SOLR-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta resolved SOLR-6391. Resolution: Fixed > Improve message for CREATECOLLECTION failure due to missing numShards >

[jira] [Commented] (SOLR-6379) CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105837#comment-14105837 ] Anshum Gupta commented on SOLR-6379: [~hossman] So, I'll translate the above comment as

[jira] [Commented] (SOLR-6402) OverseerCollectionProcessor should not exit for ZK ConnectionLoss

[ https://issues.apache.org/jira/browse/SOLR-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106378#comment-14106378 ] Anshum Gupta commented on SOLR-6402: bq. All ZK manipulation should be through SolrZkCl

[jira] [Commented] (SOLR-6316) API to know number of backups available

[ https://issues.apache.org/jira/browse/SOLR-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106525#comment-14106525 ] Anshum Gupta commented on SOLR-6316: [~Primož Skale] The branch for 4.10 has already be

[jira] [Updated] (SOLR-6379) CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.

[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-6379: --- Attachment: SOLR-6379.patch Tests and the patch. I have a few randomly failing tests so I'd like to ru

<    1   2   3   4   5   6   7   8   9   10   >