[jira] [Updated] (SOLR-4722) Highlighter which generates a list of query term position(s) for each item in a list of documents, or returns null if highlighting is disabled.

[ https://issues.apache.org/jira/browse/SOLR-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-4722: -- Attachment: PositionsSolrHighlighter.java Thanks a lot for the patch! I did some modification based on

[jira] [Commented] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732316#comment-15732316 ] Forest Soup commented on SOLR-9829: --- Thanks All! I have a mail thread tracking on it.

[jira] [Commented] (SOLR-9828) Very long young generation stop the world GC pause

[ https://issues.apache.org/jira/browse/SOLR-9828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732274#comment-15732274 ] Forest Soup commented on SOLR-9828: --- The mail thread:

[jira] [Commented] (SOLR-9828) Very long young generation stop the world GC pause

[ https://issues.apache.org/jira/browse/SOLR-9828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732269#comment-15732269 ] Forest Soup commented on SOLR-9828: --- Thanks Shawn, I'll use this mail thread talking on it instead of

[jira] [Updated] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9829: -- Description: When Solr meets a large GC pause like https://issues.apache.org/jira/browse/SOLR-9828 ,

[jira] [Commented] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731274#comment-15731274 ] Forest Soup commented on SOLR-9829: --- Hi Erick, I'm sure the solr node is still in the live_nodes list.

[jira] [Updated] (SOLR-9829) Solr cannot provide index service after a large GC pause but state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9829: -- Summary: Solr cannot provide index service after a large GC pause but state in ZK is still active (was:

[jira] [Updated] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9829: -- Description: When Solr meets a large GC pause like https://issues.apache.org/jira/browse/SOLR-9828 ,

[jira] [Updated] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9829: -- Description: When Solr meets a large GC pause like https://issues.apache.org/jira/browse/SOLR-9828 ,

[jira] [Updated] (SOLR-9829) Solr cannot provide index service after a large GC pause but core state in ZK is still active

[ https://issues.apache.org/jira/browse/SOLR-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9829: -- Summary: Solr cannot provide index service after a large GC pause but core state in ZK is still active

[jira] [Created] (SOLR-9829) Solr cannot provide index service after a large GC pause

Forest Soup created SOLR-9829: - Summary: Solr cannot provide index service after a large GC pause Key: SOLR-9829 URL: https://issues.apache.org/jira/browse/SOLR-9829 Project: Solr Issue Type:

[jira] [Updated] (SOLR-9825) Solr should not return HTTP 400 for some cases

[ https://issues.apache.org/jira/browse/SOLR-9825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9825: -- Affects Version/s: (was: 5.3) 5.3.2 > Solr should not return HTTP 400 for

[jira] [Updated] (SOLR-9828) Very long young generation stop the world GC pause

[ https://issues.apache.org/jira/browse/SOLR-9828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9828: -- Description: We are using oracle jdk8u92 64bit. The jvm memory related options: -Xms32768m -Xmx32768m

[jira] [Created] (SOLR-9828) Very long young generation stop the world GC pause

Forest Soup created SOLR-9828: - Summary: Very long young generation stop the world GC pause Key: SOLR-9828 URL: https://issues.apache.org/jira/browse/SOLR-9828 Project: Solr Issue Type: Bug

[jira] [Created] (SOLR-9825) Solr should not return HTTP 400 for some cases

Forest Soup created SOLR-9825: - Summary: Solr should not return HTTP 400 for some cases Key: SOLR-9825 URL: https://issues.apache.org/jira/browse/SOLR-9825 Project: Solr Issue Type: Bug

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Description: When we doing a batch of index and search operations to SolrCloud v5.3.2, we usually met a

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Attachment: threads.zip > Solr has a CPU% spike when indexing a batch of data >

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Description: When we doing a batch of index and search operations to SolrCloud v5.3.2, we usually met a

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Attachment: screenshot-1.png > Solr has a CPU% spike when indexing a batch of data >

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Description: When we doing a batch of index and search operations to SolrCloud v5.3.2, we usually met a

[jira] [Updated] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

[ https://issues.apache.org/jira/browse/SOLR-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-9741: -- Description: When we doing index a batch of data to SolrCloud v5.3.2, we usually met a CPU% spike

[jira] [Created] (SOLR-9741) Solr has a CPU% spike when indexing a batch of data

Forest Soup created SOLR-9741: - Summary: Solr has a CPU% spike when indexing a batch of data Key: SOLR-9741 URL: https://issues.apache.org/jira/browse/SOLR-9741 Project: Solr Issue Type: Bug

[jira] [Commented] (SOLR-5724) Two node, one shard solr instance intermittently going offline

[ https://issues.apache.org/jira/browse/SOLR-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434430#comment-15434430 ] Forest Soup commented on SOLR-5724: --- I found the similar issue in Solr v5.3.2 - We have a solrcloud

[jira] [Commented] (SOLR-7021) Leader will not publish core as active without recovering first, but never recovers

[ https://issues.apache.org/jira/browse/SOLR-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316424#comment-15316424 ] Forest Soup commented on SOLR-7021: --- Is there any plan to fix this? We found same log in v5.3.2

[jira] [Created] (SOLR-9173) NullPointerException during recovery

Forest Soup created SOLR-9173: - Summary: NullPointerException during recovery Key: SOLR-9173 URL: https://issues.apache.org/jira/browse/SOLR-9173 Project: Solr Issue Type: Bug

[jira] [Updated] (SOLR-8756) Need 4 config "zkDigestUsername"/"zkDigestPassword"/ solr.xml

[ https://issues.apache.org/jira/browse/SOLR-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-8756: -- Summary: Need 4 config "zkDigestUsername"/"zkDigestPassword"/ solr.xml (was: Need config

[jira] [Updated] (SOLR-8756) Need 4 config "zkDigestUsername"/"zkDigestPassword"/"zkDigestReadonlyUsername"/"zkDigestReadonlyUsername" in solr.xml

[ https://issues.apache.org/jira/browse/SOLR-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-8756: -- Summary: Need 4 config

[jira] [Updated] (SOLR-8756) Need 4 config "zkDigestUsername"/"zkDigestPassword"/"zkDigestReadonlyUsername"/ solr.xml

[ https://issues.apache.org/jira/browse/SOLR-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-8756: -- Summary: Need 4 config "zkDigestUsername"/"zkDigestPassword"/"zkDigestReadonlyUsername"/ solr.xml

[jira] [Created] (SOLR-8756) Need config "zkDigestUsername" and "zkDigestPassword" in /solr.xml

Forest Soup created SOLR-8756: - Summary: Need config "zkDigestUsername" and "zkDigestPassword" in /solr.xml Key: SOLR-8756 URL: https://issues.apache.org/jira/browse/SOLR-8756 Project: Solr

[jira] [Updated] (SOLR-8756) Need config "zkDigestUsername" and "zkDigestPassword" in /solr.xml

[ https://issues.apache.org/jira/browse/SOLR-8756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-8756: -- Description: Need 4 config in /solr.xml instead of -D parameter in solr.in.sh. like below:

[jira] [Updated] (SOLR-7982) SolrCloud: collection creation: There are duplicate coreNodeName in core.properties in a same collection.

[ https://issues.apache.org/jira/browse/SOLR-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7982: -- Description: We have a 3 Zookeeper 5 solr server Solrcloud. We created collection1 and collection2 with

[jira] [Updated] (SOLR-7982) SolrCloud: collection creation: There are duplicate coreNodeName in core.properties in a same collection.

[ https://issues.apache.org/jira/browse/SOLR-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7982: -- Summary: SolrCloud: collection creation: There are duplicate coreNodeName in core.properties in a same

[jira] [Created] (SOLR-7982) SolrCloud: There are duplicate coreNodeName in core.properties in a same collection after the collection is created.

Forest Soup created SOLR-7982: - Summary: SolrCloud: There are duplicate coreNodeName in core.properties in a same collection after the collection is created. Key: SOLR-7982 URL:

[jira] [Updated] (SOLR-7982) SolrCloud: collection creation: There are duplicate coreNodeName in core.properties in a same collection.

[ https://issues.apache.org/jira/browse/SOLR-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7982: -- Description: We have a 3 Zookeeper 5 solr server Solrcloud. We created collection1 and collection2 with

[jira] [Updated] (SOLR-7947) SolrCloud: /live_nodes in ZK shows the server is there, but all cores are down in /clusterstate.json.

[ https://issues.apache.org/jira/browse/SOLR-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7947: -- Description: A SolrCloud with 2 solr node in Tomcat server on 2 VM servers. After restart one solr

[jira] [Updated] (SOLR-7947) SolrCloud: /live_nodes in ZK shows the server is there, but all cores are down in /clusterstate.json.

[ https://issues.apache.org/jira/browse/SOLR-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7947: -- Summary: SolrCloud: /live_nodes in ZK shows the server is there, but all cores are down in

[jira] [Created] (SOLR-7947) ZooKeeper /live_nodes shows the server is there, but all cores are down in /clusterstate.json.

Forest Soup created SOLR-7947: - Summary: ZooKeeper /live_nodes shows the server is there, but all cores are down in /clusterstate.json. Key: SOLR-7947 URL: https://issues.apache.org/jira/browse/SOLR-7947

[jira] [Updated] (SOLR-7947) SolrCloud: after a solr node restarted, all cores in the node are down in /clusterstate.json due to java.nio.channels.OverlappingFileLockException.

[ https://issues.apache.org/jira/browse/SOLR-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7947: -- Summary: SolrCloud: after a solr node restarted, all cores in the node are down in /clusterstate.json

[jira] [Updated] (SOLR-7947) SolrCloud: /live_nodes in ZK shows the server is there, but all cores are down in /clusterstate.json.

[ https://issues.apache.org/jira/browse/SOLR-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7947: -- Attachment: solr.zip SolrCloud: /live_nodes in ZK shows the server is there, but all cores are down

[jira] [Commented] (SOLR-5692) StackOverflowError during SolrCloud leader election process

[ https://issues.apache.org/jira/browse/SOLR-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541343#comment-14541343 ] Forest Soup commented on SOLR-5692: --- I met the same issue within Solr 4.7.0. Too many

[jira] [Commented] (SOLR-6213) StackOverflowException in Solr cloud's leader election

[ https://issues.apache.org/jira/browse/SOLR-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541349#comment-14541349 ] Forest Soup commented on SOLR-6213: --- Can we set a max re-try number instead of keep

[jira] [Updated] (SOLR-6213) StackOverflowException in Solr cloud's leader election

[ https://issues.apache.org/jira/browse/SOLR-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6213: -- Attachment: stackoverflow.txt The stackoverflow exception. StackOverflowException in Solr cloud's

[jira] [Comment Edited] (SOLR-6213) StackOverflowException in Solr cloud's leader election

[ https://issues.apache.org/jira/browse/SOLR-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541359#comment-14541359 ] Forest Soup edited comment on SOLR-6213 at 5/13/15 5:27 AM: The

[jira] [Commented] (SOLR-6213) StackOverflowException in Solr cloud's leader election

[ https://issues.apache.org/jira/browse/SOLR-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541350#comment-14541350 ] Forest Soup commented on SOLR-6213: --- I met the same issue within Solr 4.7.0. Too many

[jira] [Commented] (SOLR-6156) Exception while using group with timeAllowed on SolrCloud.

[ https://issues.apache.org/jira/browse/SOLR-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506695#comment-14506695 ] Forest Soup commented on SOLR-6156: --- We have the same issue, when we issue a request like

[jira] [Comment Edited] (SOLR-6156) Exception while using group with timeAllowed on SolrCloud.

[ https://issues.apache.org/jira/browse/SOLR-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506695#comment-14506695 ] Forest Soup edited comment on SOLR-6156 at 4/22/15 9:20 AM: We

[jira] [Updated] (SOLR-7434) Adding coreName to each log entry

[ https://issues.apache.org/jira/browse/SOLR-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7434: -- Affects Version/s: 5.1 Adding coreName to each log entry -

[jira] [Updated] (SOLR-7434) Adding coreName to each log entry

[ https://issues.apache.org/jira/browse/SOLR-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7434: -- Affects Version/s: (was: 5.1) 4.7 Adding coreName to each log entry

[jira] [Created] (SOLR-7434) Adding coreName to each log entry

Forest Soup created SOLR-7434: - Summary: Adding coreName to each log entry Key: SOLR-7434 URL: https://issues.apache.org/jira/browse/SOLR-7434 Project: Solr Issue Type: Improvement

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381798#comment-14381798 ] Forest Soup commented on SOLR-6359: --- We have a SolrCloud with 5 solr servers of Solr

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381799#comment-14381799 ] Forest Soup commented on SOLR-6359: --- It looks like

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381798#comment-14381798 ] Forest Soup edited comment on SOLR-6359 at 3/26/15 2:21 PM: We

[jira] [Issue Comment Deleted] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6359: -- Comment: was deleted (was: It looks like https://issues.apache.org/jira/browse/SOLR-4605, but I guess

[jira] [Updated] (SOLR-7292) OutOfMemory happened in Solr, but /clusterstates.json shows cores active

[ https://issues.apache.org/jira/browse/SOLR-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7292: -- Attachment: OOM.txt failure.txt OutOfMemory happened in Solr, but /clusterstates.json

[jira] [Created] (SOLR-7292) When there is OutOfMemory happened in Solr and Solr cannot do update, but the /clusterstates.json on ZooKeeper still shows it is active

Forest Soup created SOLR-7292: - Summary: When there is OutOfMemory happened in Solr and Solr cannot do update, but the /clusterstates.json on ZooKeeper still shows it is active Key: SOLR-7292 URL:

[jira] [Updated] (SOLR-7292) OutOfMemory happened in Solr, but /clusterstates.json shows cores active

[ https://issues.apache.org/jira/browse/SOLR-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7292: -- Summary: OutOfMemory happened in Solr, but /clusterstates.json shows cores active (was: When there is

[jira] [Commented] (SOLR-7292) OutOfMemory happened in Solr, but /clusterstates.json shows cores active

[ https://issues.apache.org/jira/browse/SOLR-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377084#comment-14377084 ] Forest Soup commented on SOLR-7292: --- Thank you all! Will consider your suggestion!

[jira] [Created] (SOLR-7069) A down core(shard replica) on an active node cannot failover the query to its good peer

Forest Soup created SOLR-7069: - Summary: A down core(shard replica) on an active node cannot failover the query to its good peer Key: SOLR-7069 URL: https://issues.apache.org/jira/browse/SOLR-7069

[jira] [Updated] (SOLR-7069) A down core(shard replica) on an active node cannot failover the query to its good peer

[ https://issues.apache.org/jira/browse/SOLR-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7069: -- Description: When querying a collection with a core in down state, if we send the request to the server

[jira] [Updated] (SOLR-7069) A down core(shard replica) on an active node cannot failover the query to its good peer

[ https://issues.apache.org/jira/browse/SOLR-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7069: -- Description: When querying a collection with a core in down state, if we send the request to the server

[jira] [Updated] (SOLR-7069) A down core(shard replica) on an active node cannot failover the query to its good peer

[ https://issues.apache.org/jira/browse/SOLR-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7069: -- Attachment: Untitled.png A down core on an active node. A down core(shard replica) on an active node

[jira] [Updated] (SOLR-7069) A down core(shard replica) on an active node cannot failover the query to its good peer on another server

[ https://issues.apache.org/jira/browse/SOLR-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-7069: -- Summary: A down core(shard replica) on an active node cannot failover the query to its good peer on

[jira] [Issue Comment Deleted] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6675: -- Comment: was deleted (was: We agree it's the suggester part. Thanks!) Solr webapp deployment is very

[jira] [Commented] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288613#comment-14288613 ] Forest Soup commented on SOLR-6675: --- We agree it's the suggester part. Thanks! Solr

[jira] [Commented] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288614#comment-14288614 ] Forest Soup commented on SOLR-6675: --- We agree it's the suggester part. Thanks! Solr

[jira] [Issue Comment Deleted] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6359: -- Comment: was deleted (was: Thanks. But will there be this case? After a snapshot recovery of core A is

[jira] [Commented] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263806#comment-14263806 ] Forest Soup commented on SOLR-6683: --- The snapshot recovery does not clear tlog of the

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263807#comment-14263807 ] Forest Soup commented on SOLR-6359: --- The snapshot recovery does not clear tlog of the

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264276#comment-14264276 ] Forest Soup commented on SOLR-6359: --- Thanks. But will there be this case? After a

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264277#comment-14264277 ] Forest Soup commented on SOLR-6359: --- Thanks. But will there be this case? After a

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264277#comment-14264277 ] Forest Soup edited comment on SOLR-6359 at 1/5/15 7:27 AM: ---

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263763#comment-14263763 ] Forest Soup commented on SOLR-6359: --- it works but with some pre-condition: the 20% newest

[jira] [Commented] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263762#comment-14263762 ] Forest Soup commented on SOLR-6683: --- it works but with some pre-condition: the 20% newest

[jira] [Commented] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263765#comment-14263765 ] Forest Soup commented on SOLR-6683: --- A full snapshot recovery does not clean the tlog of

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263764#comment-14263764 ] Forest Soup commented on SOLR-6359: --- A full snapshot recovery does not clean the tlog of

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249827#comment-14249827 ] Forest Soup edited comment on SOLR-6359 at 1/4/15 6:18 AM: --- I

[jira] [Comment Edited] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249826#comment-14249826 ] Forest Soup edited comment on SOLR-6683 at 1/4/15 6:18 AM: --- I

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249827#comment-14249827 ] Forest Soup edited comment on SOLR-6359 at 1/4/15 6:19 AM: --- I

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246618#comment-14246618 ] Forest Soup edited comment on SOLR-6359 at 12/17/14 7:59 AM: -

[jira] [Comment Edited] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246618#comment-14246618 ] Forest Soup edited comment on SOLR-6359 at 12/17/14 10:01 AM: --

[jira] [Commented] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249826#comment-14249826 ] Forest Soup commented on SOLR-6683: --- I applied the patch for SOLR-6359 on 4.7 and did

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249827#comment-14249827 ] Forest Soup commented on SOLR-6359: --- I applied the patch for SOLR-6359 on 4.7 and did

[jira] [Commented] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246497#comment-14246497 ] Forest Soup commented on SOLR-6675: --- Looks like thread searcherExecutor-5-thread-1 and

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246505#comment-14246505 ] Forest Soup commented on SOLR-6359: --- Is the patch only available for Solr 5.0? For Solr

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246609#comment-14246609 ] Forest Soup commented on SOLR-6359: --- When could we get the official build with that patch

[jira] [Commented] (SOLR-6359) Allow customization of the number of records and logs kept by UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246618#comment-14246618 ] Forest Soup commented on SOLR-6359: --- And where should I set the numRecordsToKeep and

[jira] [Updated] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6675: -- Attachment: 1014.zip The 0001.txt and 0002.txt are the dump files before solr webapp is deployed. The

[jira] [Commented] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234034#comment-14234034 ] Forest Soup commented on SOLR-6675: --- This is our JVM. And we have never tried the latest

[jira] [Commented] (SOLR-4470) Support for basic http auth in internal solr requests

[ https://issues.apache.org/jira/browse/SOLR-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234046#comment-14234046 ] Forest Soup commented on SOLR-4470: --- Does anyone have an idea when this will be released?

[jira] [Commented] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234052#comment-14234052 ] Forest Soup commented on SOLR-6683: --- Thanks, Ramkumar. We will try it. Thanks! Need a

[jira] [Created] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

Forest Soup created SOLR-6683: - Summary: Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery Key: SOLR-6683 URL: https://issues.apache.org/jira/browse/SOLR-6683

[jira] [Updated] (SOLR-6683) Need a configurable parameter to control the doc number between peersync and the snapshot pull recovery

[ https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6683: -- Description: If there are 100 docs gap between the recovering node and the good node, the solr will do

[jira] [Created] (SOLR-6674) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

Forest Soup created SOLR-6674: - Summary: Solr webapp deployment is very slow with jmx/ in solrconfig.xml Key: SOLR-6674 URL: https://issues.apache.org/jira/browse/SOLR-6674 Project: Solr Issue

[jira] [Created] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

Forest Soup created SOLR-6675: - Summary: Solr webapp deployment is very slow with jmx/ in solrconfig.xml Key: SOLR-6675 URL: https://issues.apache.org/jira/browse/SOLR-6675 Project: Solr Issue

[jira] [Commented] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189798#comment-14189798 ] Forest Soup commented on SOLR-6675: --- The catalina log of tomcat: INFO: Starting Servlet

[jira] [Comment Edited] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189802#comment-14189802 ] Forest Soup edited comment on SOLR-6675 at 10/30/14 8:33 AM: -

[jira] [Updated] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6675: -- Attachment: callstack.png The call stack of the long blocking thread which is doing statistics

[jira] [Updated] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6675: -- Description: We have a SolrCloud with Solr version 4.7 with Tomcat 7. And our solr index(cores) are

[jira] [Updated] (SOLR-6675) Solr webapp deployment is very slow with jmx/ in solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forest Soup updated SOLR-6675: -- Description: We have a SolrCloud with Solr version 4.7 with Tomcat 7. And our solr index(cores) are

[jira] [Commented] (SOLR-6335) org.apache.solr.common.SolrException: no servers hosting shard

[ https://issues.apache.org/jira/browse/SOLR-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092340#comment-14092340 ] Forest Soup commented on SOLR-6335: --- Thanks Erick. Before I open JIRA, I have searched,

  1   2   >