[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=13876232#comment-13876232 ] Shalin Shekhar Mangar commented on SOLR-5477: - Some comments on the last patch:

[jira] [Updated] (SOLR-5646) SolrEventListener listener should have destroy function

[ https://issues.apache.org/jira/browse/SOLR-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raintung Li updated SOLR-5646: -- Attachment: patch-5646 > SolrEventListener listener should have destroy function > -

[jira] [Updated] (LUCENE-5395) Upgrade Spatial4j to 0.4

[ https://issues.apache.org/jira/browse/LUCENE-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-5395: - Attachment: LUCENE-5395_Spatial4j_0_4.patch Patch attached. It was a bit of work because I ween

Re: [VOTE] Release Lucene/Solr 4.6.1 RC2

When running the smoke tester against RC2, I ran into the same test problem that Simon fixed a week ago on branch_4x, but not on lucene_solr_4_6: [ http://svn.apache.org/r1557503]. My log is below. Not worth a respin IMHO. Running smoke tester again. - [junit4] Suite: org.apache.lucene.s

[jira] [Commented] (LUCENE-5092) join: don't expect all filters to be FixedBitSet instances

[ https://issues.apache.org/jira/browse/LUCENE-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876136#comment-13876136 ] Mikhail Khludnev commented on LUCENE-5092: -- It seems great! > join: don't expec

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876126#comment-13876126 ] Mark Miller commented on SOLR-5608: --- Nope, still more to do here... > Frequently reprodu

[jira] [Created] (SOLR-5646) SolrEventListener listener should have destroy function

Raintung Li created SOLR-5646: - Summary: SolrEventListener listener should have destroy function Key: SOLR-5646 URL: https://issues.apache.org/jira/browse/SOLR-5646 Project: Solr Issue Type: Impr

[jira] [Commented] (SOLR-5643) ConcurrentUpdateSolrServer will sometimes not spawn a new Runner thread even though there are updates in the queue.

[ https://issues.apache.org/jira/browse/SOLR-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876109#comment-13876109 ] ASF subversion and git services commented on SOLR-5643: --- Commit 15596

[jira] [Commented] (SOLR-5643) ConcurrentUpdateSolrServer will sometimes not spawn a new Runner thread even though there are updates in the queue.

[ https://issues.apache.org/jira/browse/SOLR-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876110#comment-13876110 ] ASF subversion and git services commented on SOLR-5643: --- Commit 15596

[VOTE] Release Lucene/Solr 4.6.1 RC2

Please vote to release the following artifacts: http://people.apache.org/~markrmiller/lucene_solr_4_6_1r1559610/ Here is my +1. SUCCESS! [0:51:51.964657] -- - Mark

[VOTE] Release Lucene/Solr 4.6.1 RC2

Please vote to release the following artifacts: http://people.apache.org/~markrmiller/lucene_solr_4_6_1r1559610/ Here is my +1. SUCCESS! [0:51:51.964657] -- - Mark

[jira] [Assigned] (SOLR-5643) ConcurrentUpdateSolrServer will sometimes not spawn a new Runner thread even though there are updates in the queue.

[ https://issues.apache.org/jira/browse/SOLR-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller reassigned SOLR-5643: - Assignee: Mark Miller > ConcurrentUpdateSolrServer will sometimes not spawn a new Runner thread ev

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

Should have been in my experience, not imo - have had a cold for a week and it’s getting to me. bq. it could use the information it's been given about java 6. I think it’s an Apache Ant thing. JAVA6_HOME and JAVA7_HOME are Lucene smoke tester things. - Mark On Jan 19, 2014, at 9:02 PM, Shawn

[jira] [Updated] (SOLR-5643) ConcurrentUpdateSolrServer will sometimes not spawn a new Runner thread even though there are updates in the queue.

[ https://issues.apache.org/jira/browse/SOLR-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5643: -- Attachment: SOLR-5643.patch I think that this will address it. I've been testing it with a case that I

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

On 1/19/2014 4:04 PM, Mark Miller wrote: > If you are building the artifacts, you have to make sure it's using Java > 6 rather than 7. IMO on linux, ant picks up what is set by the JAVA_HOME > env variable. The /etc/alternatives links point all the main java executables to 7u25. 6u26 is available

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876051#comment-13876051 ] ASF subversion and git services commented on SOLR-5608: --- Commit 15596

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876052#comment-13876052 ] ASF subversion and git services commented on SOLR-5608: --- Commit 15596

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876050#comment-13876050 ] ASF subversion and git services commented on SOLR-5608: --- Commit 15596

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876049#comment-13876049 ] Mark Miller commented on SOLR-5608: --- *now* I think I've gotten it ;) > Frequently reprod

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876046#comment-13876046 ] ASF subversion and git services commented on SOLR-5608: --- Commit 15596

[jira] [Commented] (SOLR-5608) Frequently reproducible failures in CollectionsAPIDistributedZkTest#testDistribSearch

[ https://issues.apache.org/jira/browse/SOLR-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876047#comment-13876047 ] ASF subversion and git services commented on SOLR-5608: --- Commit 15596

RE: [VOTE] Release Lucene/Solr 4.6.1 RC1

Hi Mark, This problem lets me remember LUCENE-5355: This one affected the “nice” javadocs created after release. I backported the patch, so the one running the “nice looking javadocs” on java 7 with java 6 bootclasspath can be sure, it was really using the correct bootclasspath. Also the doc

[jira] [Commented] (LUCENE-5355) Add more support to validate the -Dbootclasspath given for javadocs generate

[ https://issues.apache.org/jira/browse/LUCENE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876044#comment-13876044 ] ASF subversion and git services commented on LUCENE-5355: - Commit

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

If you are building the artifacts, you have to make sure it's using Java 6 rather than 7. IMO on linux, ant picks up what is set by the JAVA_HOME env variable. - Mark On Sun, Jan 19, 2014 at 5:57 PM, Shawn Heisey wrote: > On 1/19/2014 12:59 PM, Mark Miller wrote: > > Unfortunately, I think SOL

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

On 1/19/2014 12:59 PM, Mark Miller wrote: > Unfortunately, I think SOLR-5645 is probably worth a re spin. I think > otherwise, collection reloads will be unstable vs 4.6. Collection reloads were unstable once before, SOLR-4805. A lot of people were hit by that one. I was very glad when SOLR-4805

[jira] [Comment Edited] (LUCENE-5404) Add support to get number of entries a Suggester Lookup was built with and minor refactorings

[ https://issues.apache.org/jira/browse/LUCENE-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876033#comment-13876033 ] Areek Zillur edited comment on LUCENE-5404 at 1/19/14 10:36 PM: ---

[jira] [Updated] (LUCENE-5404) Add support to get number of entries a Suggester Lookup was built with and minor refactorings

[ https://issues.apache.org/jira/browse/LUCENE-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Areek Zillur updated LUCENE-5404: - Attachment: LUCENE-5404.patch Updated Patch: - count() -> getCount() - doc to make it clear

[jira] [Commented] (LUCENE-5092) join: don't expect all filters to be FixedBitSet instances

[ https://issues.apache.org/jira/browse/LUCENE-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876032#comment-13876032 ] Paul Elschot commented on LUCENE-5092: -- There is an early version of DocBlockIterato

[jira] [Resolved] (SOLR-5633) HttpShardHandlerFactory should make its http client available to subclasses

[ https://issues.apache.org/jira/browse/SOLR-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-5633. --- Resolution: Fixed > HttpShardHandlerFactory should make its http client available to subclasses >

[jira] [Updated] (SOLR-5633) HttpShardHandlerFactory should make its http client available to subclasses

[ https://issues.apache.org/jira/browse/SOLR-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5633: -- Fix Version/s: 4.7 5.0 > HttpShardHandlerFactory should make its http client availabl

[jira] [Updated] (LUCENE-5099) QueryNode should have the ability to detach from its node parent

[ https://issues.apache.org/jira/browse/LUCENE-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani updated LUCENE-5099: - Attachment: LUCENE-5099_adrianocrestani_2014-01-19.patch LUCENE-5099_adri

[jira] [Commented] (LUCENE-5099) QueryNode should have the ability to detach from its node parent

[ https://issues.apache.org/jira/browse/LUCENE-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876016#comment-13876016 ] Adriano Crestani commented on LUCENE-5099: -- After some investigation, I reached

[jira] [Updated] (LUCENE-5099) QueryNode should have the ability to detach from its node parent

[ https://issues.apache.org/jira/browse/LUCENE-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani updated LUCENE-5099: - Summary: QueryNode should have the ability to detach from its node parent (was: QueryNo

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876014#comment-13876014 ] ASF subversion and git services commented on SOLR-5577: --- Commit 15595

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876015#comment-13876015 ] ASF subversion and git services commented on SOLR-5577: --- Commit 15595

[jira] [Commented] (SOLR-5577) indexing delay due to zookeeper election

[ https://issues.apache.org/jira/browse/SOLR-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876013#comment-13876013 ] ASF subversion and git services commented on SOLR-5577: --- Commit 15595

Re: svn commit: r1559318 - in /lucene/dev/branches/lucene_solr_4_6/lucene: ./ queryparser/src/java/org/apache/lucene/queryparser/flexible/standard/processors/ queryparser/src/test/org/apache/lucene/qu

Nice. Thanks Mark ;) On Sun, Jan 19, 2014 at 3:08 PM, Mark Miller wrote: > > On Jan 18, 2014, at 10:03 PM, Adriano Crestani > wrote: > > Thanks for letting me know. So it will be pushed automatically to 4.6.2, > right?! > > > Right. > > All we will need to do is change the CHANGES.txt. > > > R

[jira] [Commented] (SOLR-5636) SolrRequestParsers does some xpath lookups on every request.

[ https://issues.apache.org/jira/browse/SOLR-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876008#comment-13876008 ] ASF subversion and git services commented on SOLR-5636: --- Commit 15595

[jira] [Commented] (SOLR-5636) SolrRequestParsers does some xpath lookups on every request.

[ https://issues.apache.org/jira/browse/SOLR-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876009#comment-13876009 ] ASF subversion and git services commented on SOLR-5636: --- Commit 15595

[jira] [Commented] (SOLR-5636) SolrRequestParsers does some xpath lookups on every request.

[ https://issues.apache.org/jira/browse/SOLR-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876007#comment-13876007 ] ASF subversion and git services commented on SOLR-5636: --- Commit 15595

[jira] [Updated] (SOLR-5636) SolrRequestParsers does some xpath lookups on every request.

[ https://issues.apache.org/jira/browse/SOLR-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5636: -- Fix Version/s: 4.6.1 This might as well go into a 4.6.1 respin. > SolrRequestParsers does some xpath lo

[jira] [Commented] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876003#comment-13876003 ] ASF subversion and git services commented on SOLR-5645: --- Commit 15595

[jira] [Commented] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876001#comment-13876001 ] ASF subversion and git services commented on SOLR-5645: --- Commit 15595

[jira] [Commented] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875998#comment-13875998 ] ASF subversion and git services commented on SOLR-5645: --- Commit 15595

Re: svn commit: r1559318 - in /lucene/dev/branches/lucene_solr_4_6/lucene: ./ queryparser/src/java/org/apache/lucene/queryparser/flexible/standard/processors/ queryparser/src/test/org/apache/lucene/qu

On Jan 18, 2014, at 10:03 PM, Adriano Crestani wrote: > Thanks for letting me know. So it will be pushed automatically to 4.6.2, > right?! Right. > All we will need to do is change the CHANGES.txt. Right. Though it looks like we should re spin 4.6.1, in which case it will be included. - M

[jira] [Updated] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5645: -- Description: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-MacOSX/1211/ > A SolrCore reload via the Cor

[jira] [Updated] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-5645: -- Fix Version/s: 4.6.1 > A SolrCore reload via the CoreContainer will try and register in zk again > with

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

Unfortunately, I think SOLR-5645 is probably worth a re spin. I think otherwise, collection reloads will be unstable vs 4.6. On Sat, Jan 18, 2014 at 10:29 AM, Sanne Grinovero wrote: > +1 > > Run integration tests with: > - Hibernate Search > - Infinispan (indexing/searching entries with Lucen

[jira] [Commented] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875994#comment-13875994 ] Mark Miller commented on SOLR-5645: --- I almost think we should re roll 4.6.1 for this...

[JENKINS] Lucene-Solr-4.x-MacOSX (64bit/jdk1.7.0) - Build # 1213 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-MacOSX/1213/ Java: 64bit/jdk1.7.0 -XX:-UseCompressedOops -XX:+UseG1GC 1 tests failed. REGRESSION: org.apache.solr.core.TestNonNRTOpen.testReaderIsNotNRT Error Message: expected:<3> but was:<2> Stack Trace: java.lang.AssertionError: expected:

[jira] [Created] (SOLR-5645) A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore.

Mark Miller created SOLR-5645: - Summary: A SolrCore reload via the CoreContainer will try and register in zk again with the new SolrCore. Key: SOLR-5645 URL: https://issues.apache.org/jira/browse/SOLR-5645

[jira] [Commented] (LUCENE-5376) Add a demo search server

[ https://issues.apache.org/jira/browse/LUCENE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875958#comment-13875958 ] ASF subversion and git services commented on LUCENE-5376: - Commit

Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b123) - Build # 9152 - Failure!

Hi Uwe, Can you get a bug logged , include that log etc. let me know the incident number and I will move it along. Should mention that unfortunately it's not reproducible! Thanks Rory On 19/01/2014 12:10, Uwe Schindler wrote: As always, h_err is here: http://jenkins.thetaphi.de/job/Lucene-

[jira] [Created] (SOLR-5644) SplitShard does not handle not finding a shard leader well.

Mark Miller created SOLR-5644: - Summary: SplitShard does not handle not finding a shard leader well. Key: SOLR-5644 URL: https://issues.apache.org/jira/browse/SOLR-5644 Project: Solr Issue Type:

[jira] [Commented] (LUCENE-5376) Add a demo search server

[ https://issues.apache.org/jira/browse/LUCENE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875921#comment-13875921 ] ASF subversion and git services commented on LUCENE-5376: - Commit

[jira] [Updated] (SOLR-5526) Query parser extends standard cause NPE on Solr startup

[ https://issues.apache.org/jira/browse/SOLR-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Zhovtyuk updated SOLR-5526: --- Attachment: NPE_load_trace NPE stacktrace during solr load > Query parser extends standard ca

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1083: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1083/ 2 tests failed. REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch Error Message: null Stack Trace: java.lang.AssertionError: null at __randomizedtesting.SeedInfo.seed([F96643ADFB7282F4

RE: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b123) - Build # 9152 - Failure!

As always, h_err is here: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/9152/artifact/lucene/build/core/test/J1/hs_err_pid15321.log Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From:

RE: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b123) - Build # 9152 - Failure!

Hi all, hi Rory, New bug (not reproduceable) in JDK 8 b123, 32 bits: This one happened in the GC thread (ConcMarkSweep GC). All other threads are “blocked”, except the VM itself and the GCTaskThread, which segfaulted. So it seemed to happen on a full stop-the-world GC run (otherwise Java thr

Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b123) - Build # 9152 - Failure!

This is a new one. Policeman Jenkins Server schrieb: >Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/9152/ >Java: 32bit/jdk1.8.0-ea-b123 -server -XX:+UseConcMarkSweepGC > >All tests passed > >Build Log: >[...truncated 1221 lines...] >[junit4] JVM J1: stdout was not empty, see: >/mn

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0-ea-b123) - Build # 9152 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/9152/ Java: 32bit/jdk1.8.0-ea-b123 -server -XX:+UseConcMarkSweepGC All tests passed Build Log: [...truncated 1221 lines...] [junit4] JVM J1: stdout was not empty, see: /mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/lucene/build