[jira] [Commented] (SOLR-7016) techproducts example does not start on windows with "solr.cmd -e techproducts" if install dir contains whitespace

[ https://issues.apache.org/jira/browse/SOLR-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291514#comment-14291514 ] Anshum Gupta commented on SOLR-7016: This might help : http://stackoverflow.com/questi

[jira] [Commented] (SOLR-7016) techproducts example does not start on windows with "solr.cmd -e techproducts" if install dir contains whitespace

[ https://issues.apache.org/jira/browse/SOLR-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291508#comment-14291508 ] Anshum Gupta commented on SOLR-7016: I tried running this on an AWS windows instance (I

[jira] [Commented] (LUCENE-2562) Make Luke a Lucene/Solr Module

[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291506#comment-14291506 ] Tomoko Uchida commented on LUCENE-2562: --- Hi Mark, Thank you for the response! My p

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2544 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2544/ 6 tests failed. REGRESSION: org.apache.solr.handler.TestBlobHandler.doBlobHandlerTest Error Message: {responseHeader={status=0, QTime=0}, response={numFound=0, start=0, docs=[]}} Stack Trace: java.lang.AssertionError: {respo

[jira] [Updated] (SOLR-7035) Core reload calls firstSearcher listeners twice in some situations

[ https://issues.apache.org/jira/browse/SOLR-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomás Fernández Löbbe updated SOLR-7035: Attachment: SOLR-7035-fail.patch In this patch, there is a test that fails if the fir

[jira] [Created] (SOLR-7035) Core reload calls firstSearcher listeners twice in some situations

Tomás Fernández Löbbe created SOLR-7035: --- Summary: Core reload calls firstSearcher listeners twice in some situations Key: SOLR-7035 URL: https://issues.apache.org/jira/browse/SOLR-7035 Project:

[jira] [Commented] (SOLR-6707) Recovery/election for invalid core results in rapid-fire re-attempts until /overseer/queue is clogged

[ https://issues.apache.org/jira/browse/SOLR-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291437#comment-14291437 ] Mark Miller commented on SOLR-6707: --- Some of this is probably related to SOLR-7033. > Re

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2543 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2543/ 5 tests failed. FAILED: org.apache.solr.cloud.HttpPartitionTest.test Error Message: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://127.0.0.1:53674/yz_v/qg/c8n_1x2_shar

[jira] [Created] (SOLR-7034) Consider allowing any node to become leader, regardless of their last published state.

Mark Miller created SOLR-7034: - Summary: Consider allowing any node to become leader, regardless of their last published state. Key: SOLR-7034 URL: https://issues.apache.org/jira/browse/SOLR-7034 Project:

[jira] [Updated] (SOLR-7033) RecoveryStrategy should not publish any state when closed / cancelled.

[ https://issues.apache.org/jira/browse/SOLR-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-7033: -- Attachment: SOLR-7033.patch > RecoveryStrategy should not publish any state when closed / cancelled. > --

[jira] [Created] (SOLR-7033) RecoveryStrategy should not publish any state when closed / cancelled.

Mark Miller created SOLR-7033: - Summary: RecoveryStrategy should not publish any state when closed / cancelled. Key: SOLR-7033 URL: https://issues.apache.org/jira/browse/SOLR-7033 Project: Solr

[jira] [Commented] (SOLR-6707) Recovery/election for invalid core results in rapid-fire re-attempts until /overseer/queue is clogged

[ https://issues.apache.org/jira/browse/SOLR-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291421#comment-14291421 ] Mark Miller commented on SOLR-6707: --- bq. ERROR cloud.RecoveryStrategy - No UpdateLog fo

[JENKINS] Lucene-Solr-NightlyTests-5.x - Build # 744 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/744/ 7 tests failed. REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.test Error Message: shard3 is not consistent. Got 74 from https://127.0.0.1:43403/_cv/i/collection1lastClient and got 79 from https://127.0.0.1:43

[jira] [Commented] (SOLR-7030) replicas goes in recovery mode right after update

[ https://issues.apache.org/jira/browse/SOLR-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291316#comment-14291316 ] Vijay Sekhri commented on SOLR-7030: I am sorry I had wrong information posted. I poste

[JENKINS] Lucene-Solr-5.x-Windows (32bit/jdk1.7.0_76) - Build # 4334 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4334/ Java: 32bit/jdk1.7.0_76 -server -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.ReplicationFactorTest.test Error Message: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to se

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2542 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2542/ 5 tests failed. FAILED: org.apache.solr.cloud.HttpPartitionTest.test Error Message: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://127.0.0.1:12365/c8n_1x2_shard1_repli

[JENKINS] Lucene-Solr-5.0-Linux (64bit/jdk1.9.0-ea-b47) - Build # 48 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.0-Linux/48/ Java: 64bit/jdk1.9.0-ea-b47 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.DistribCursorPagingTest Error Message: Some resources were not closed, shutdown, or r

[jira] [Commented] (SOLR-6845) Add buildOnStartup option for suggesters

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

[jira] [Commented] (SOLR-6845) Add buildOnStartup option for suggesters

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

[JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.8.0_31) - Build # 4438 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/4438/ Java: 64bit/jdk1.8.0_31 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.ReplicationFactorTest.test Error Message: org.apache.http.NoHttpResponseException: The target server failed to res

[jira] [Commented] (SOLR-7030) replicas goes in recovery mode right after update

[ https://issues.apache.org/jira/browse/SOLR-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291273#comment-14291273 ] Vijay Sekhri commented on SOLR-7030: Thank you Shawn. I have posted my question to both

[jira] [Commented] (SOLR-7032) Clean up test remnants of old-style solr.xml

[ https://issues.apache.org/jira/browse/SOLR-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291264#comment-14291264 ] Erick Erickson commented on SOLR-7032: -- ba: Bah, I thought I'd expunged all trace of t

[jira] [Updated] (SOLR-6640) ChaosMonkeySafeLeaderTest failure with CorruptIndexException

[ https://issues.apache.org/jira/browse/SOLR-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-6640: -- Attachment: corruptindex.log > ChaosMonkeySafeLeaderTest failure with CorruptIndexException > ---

[jira] [Commented] (SOLR-6640) ChaosMonkeySafeLeaderTest failure with CorruptIndexException

[ https://issues.apache.org/jira/browse/SOLR-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291248#comment-14291248 ] Mark Miller commented on SOLR-6640: --- Spoke too soon - one of the jobs did hit a corrupt i

[jira] [Commented] (SOLR-7032) Clean up test remnants of old-style solr.xml

[ https://issues.apache.org/jira/browse/SOLR-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291246#comment-14291246 ] Alan Woodward commented on SOLR-7032: - Bah, I thought I'd expunged all trace of this.

[jira] [Commented] (SOLR-6640) ChaosMonkeySafeLeaderTest failure with CorruptIndexException

[ https://issues.apache.org/jira/browse/SOLR-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291244#comment-14291244 ] Mark Miller commented on SOLR-6640: --- The Chaos Monkey tests are already in much better sh

[jira] [Commented] (LUCENE-2562) Make Luke a Lucene/Solr Module

[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291239#comment-14291239 ] Mark Miller commented on LUCENE-2562: - Hey [~Tomoko Uchida] - I still think this is a

[JENKINS] Lucene-Solr-5.x-MacOSX (64bit/jdk1.8.0) - Build # 1906 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/1906/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.DeleteReplicaTest.deleteLiveReplicaTest Error Message: Should have had a good message here Stack Trace: java.lang.Asser

[jira] [Updated] (SOLR-7032) Clean up test remnants of old-style solr.xml

[ https://issues.apache.org/jira/browse/SOLR-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-7032: - Attachment: SOLR-7032.patch Preliminary patch, all tests pass but I need to look this over a bit. T

RE: [VOTE] Release 5.0.0 RC1

In addition, on most computers you extract to your windows “Desktop” and for most users this is also using a white space (the user name has in most cases white space in the name), this is also bad user experience. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen

[jira] [Created] (SOLR-7032) Clean up test remnants of old-style solr.xml

Erick Erickson created SOLR-7032: Summary: Clean up test remnants of old-style solr.xml Key: SOLR-7032 URL: https://issues.apache.org/jira/browse/SOLR-7032 Project: Solr Issue Type: Improveme

Re: [VOTE] Release 5.0.0 RC1

I'm not really a windows user so I don't really know what's a fix for the paths with a space. May be we can either fix it or document the way to use it so that this doesn't happen (put the path in quotes or something?). The worst case, we should document that it doesn't work in such cases and the s

[jira] [Commented] (SOLR-7016) techproducts example does not start on windows with "solr.cmd -e techproducts" if install dir contains whitespace

[ https://issues.apache.org/jira/browse/SOLR-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291218#comment-14291218 ] Uwe Schindler commented on SOLR-7016: - In addition most scripts print "access denied" a

[jira] [Commented] (SOLR-7031) Fix README and CHANGES for Solr 5.0

[ https://issues.apache.org/jira/browse/SOLR-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291216#comment-14291216 ] Uwe Schindler commented on SOLR-7031: - I alos found another small thing (existent very

RE: [VOTE] Release 5.0.0 RC1

Hi, With both Java 7 and Java 8 (took much longer, of course): Java 1.7 JAVA_HOME=/home/thetaphi/jdk1.7.0_76 Java 1.8 JAVA_HOME=/home/thetaphi/jdk1.8.0_31 Ubuntu 14.04, 64bit SUCCESS! [2:21:52.553327] Unfortunately, Solr still has the problem that Windows scripts to startup/shutd

[jira] [Created] (SOLR-7031) Fix README and CHANGES for Solr 5.0

Anshum Gupta created SOLR-7031: -- Summary: Fix README and CHANGES for Solr 5.0 Key: SOLR-7031 URL: https://issues.apache.org/jira/browse/SOLR-7031 Project: Solr Issue Type: Bug Componen

Re: [VOTE] Release 5.0.0 RC1

Honestly, I wouldn't prefer mentioning _how to_ get started in the CHANGES.txt. instead have it in README. We already have that duplicated in multiple places like CHANGES.txt, README.txt, quickstart.html, Ref guide etc. We should just remove that section I think or at the most just point towards o

[jira] [Updated] (SOLR-6635) Cursormark should support skipping/goto functionality

[ https://issues.apache.org/jira/browse/SOLR-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Zhovtyuk updated SOLR-6635: --- Attachment: SOLR-6635.patch As i understood skip case its about using skip to calculate next cu

Re: [VOTE] Release 5.0.0 RC1

Thanks for mentioning that Uwe. On Sun, Jan 25, 2015 at 6:52 AM, Uwe Schindler wrote: > Hey, > > > > if you have Java 8 on your machine, too, you can smoke with both (Java 7 > and Java 8): > > > > python3 dev-tools/scripts/smokeTestRelease.py --test-java8 /path/to/jdk8 > http://people.apache.org

Re: [VOTE] Release 5.0.0 RC1

+1 for that re-spin but I'd also give it a day to see if we find more issues there. If everyone wants me to just re-spin it only with this fix, I'm fine with that too. On Sun, Jan 25, 2015 at 5:43 AM, Erik Hatcher wrote: > First, thanks Anshum for taking the release bull by the horns. Lucene an

[jira] [Closed] (SOLR-7030) replicas goes in recovery mode right after update

[ https://issues.apache.org/jira/browse/SOLR-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey closed SOLR-7030. -- Resolution: Invalid > replicas goes in recovery mode right after update > ---

[jira] [Commented] (SOLR-7030) replicas goes in recovery mode right after update

[ https://issues.apache.org/jira/browse/SOLR-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291194#comment-14291194 ] Shawn Heisey commented on SOLR-7030: This should have been brought up on the mailing li

[JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 1948 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/1948/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.TestReplicaProperties.test Error Message: No live SolrServers available to handle this request:[https://127.0.0.1:54871

Update of Java Versions on Policemen Jenkins

Hi all, I updated the Policeman Jenkins server to test the following Java versions with Lucene/Solr: - jdk1.7.0_76 (Linux, OSX, Windows) - jdk1.7.0_80-ea-b05 (Linux) - jdk1.8.0_31 (Linux, OSX, Windows) - jdk1.8.0_40-ea-b22 (Linux) - jdk1.9.0-ea-b47 (Linux) Uwe - Uwe Schindler H.-H.-Meier-A

[jira] [Commented] (SOLR-6902) Use JUnit rules instead of inheritance with distributed Solr tests to allow for multiple tests without the same class

[ https://issues.apache.org/jira/browse/SOLR-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291149#comment-14291149 ] ASF GitHub Bot commented on SOLR-6902: -- Github user andyetitmoves closed the pull requ

[GitHub] lucene-solr pull request: Remove copy of .war in dist, rename exam...

Github user andyetitmoves closed the pull request at: https://github.com/apache/lucene-solr/pull/112 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the fea

[GitHub] lucene-solr pull request: Use JUnit rules instead of inheritance w...

Github user andyetitmoves closed the pull request at: https://github.com/apache/lucene-solr/pull/121 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the fea

[jira] [Commented] (SOLR-4792) stop shipping a war in 5.0

[ https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291146#comment-14291146 ] ASF GitHub Bot commented on SOLR-4792: -- Github user andyetitmoves closed the pull requ

[JENKINS] Lucene-Solr-5.x-Linux (32bit/jdk1.9.0-ea-b47) - Build # 11520 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/11520/ Java: 32bit/jdk1.9.0-ea-b47 -client -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.RecoveryAfterSoftCommitTest.test Error Message: Didn't see all replicas for shard shard1 in collection1 come up within 3 ms!

[jira] [Created] (SOLR-7030) replicas goes in recovery mode right after update

Vijay Sekhri created SOLR-7030: -- Summary: replicas goes in recovery mode right after update Key: SOLR-7030 URL: https://issues.apache.org/jira/browse/SOLR-7030 Project: Solr Issue Type: Bug

RE: [VOTE] Release 5.0.0 RC1

Hey, if you have Java 8 on your machine, too, you can smoke with both (Java 7 and Java 8): python3 dev-tools/scripts/smokeTestRelease.py --test-java8 /path/to/jdk8 http://people.apache.org/~anshum/staging_area/lucene-solr-5.0.0-RC1-rev1654615 I am doing that at the moment to ensure al

[JENKINS] Lucene-Solr-5.x-Windows (32bit/jdk1.7.0_76) - Build # 4333 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4333/ Java: 32bit/jdk1.7.0_76 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.ReplicationFactorTest.test Error Message: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_31) - Build # 11681 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11681/ Java: 64bit/jdk1.8.0_31 -XX:-UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.DistribCursorPagingTest Error Message: Suite timeout exceeded (>= 720 msec). Stack Trace:

Re: [VOTE] Release 5.0.0 RC1

First, thanks Anshum for taking the release bull by the horns. Lucene and Solr 5.0 is an exciting milestone! I’m just starting to run through RC1, and noticed a leftover now-incorrect bit in solr/CHANGES.txt. I’d say this actually warrants a respin in and of itself, alas, but of course let’s