[JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 847 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/847/ 1 tests failed. FAILED: org.apache.solr.cloud.OverseerTest.testShardLeaderChange Error Message: Could not register as the leader because creating the ephemeral registration node in ZooKeeper failed Stack Trace:

[jira] [Commented] (SOLR-8621) solrconfig.xml: deprecate/replace with

[ https://issues.apache.org/jira/browse/SOLR-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155909#comment-15155909 ] Shai Erera commented on SOLR-8621: -- Looks good [~cpoerschke]! And yes, let's be consistent and keep the

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/3045/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 3 tests failed. FAILED: org.apache.solr.cloud.TestAuthenticationFramework.testCollectionCreateWithoutCoresThenDelete Error Message: KeeperErrorCode = Session expired for

[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 418 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/418/ No tests ran. Build Log: [...truncated 39772 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist [copy]

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155890#comment-15155890 ] Mark Miller commented on SOLR-8696: --- addReplica calls create core on a node. When a core is created, it

[JENKINS] Lucene-Solr-NightlyTests-5.5 - Build # 8 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.5/8/ 3 tests failed. FAILED: org.apache.solr.cloud.hdfs.HdfsCollectionsAPIDistributedZkTest.test Error Message: Error from server at http://127.0.0.1:44582/o_lc/awholynewcollection_3: non ok status: 500, message:Server Error

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155888#comment-15155888 ] Scott Blum commented on SOLR-8696: -- [~markrmil...@gmail.com] Yes, I get the breakpoint in

[jira] [Commented] (SOLR-8708) DaemonStream should catch InterruptedException when reading underlying stream.

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

[jira] [Resolved] (SOLR-8708) DaemonStream should catch InterruptedException when reading underlying stream.

[ https://issues.apache.org/jira/browse/SOLR-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein resolved SOLR-8708. -- Resolution: Fixed > DaemonStream should catch InterruptedException when reading underlying

[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+105) - Build # 15939 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15939/ Java: 64bit/jdk-9-ea+105 -XX:+UseCompressedOops -XX:+UseParallelGC -XX:-UseSuperWord 1 tests failed. FAILED: org.apache.lucene.search.TestShardSearching.testSimple Error Message: Stack Trace: java.lang.AssertionError

[jira] [Resolved] (SOLR-8413) SolrExampleXMLTest failing reproducibly

[ https://issues.apache.org/jira/browse/SOLR-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-8413. --- Resolution: Fixed Assignee: Mark Miller Seems to be resolved with issues related to SOLR-7339.

[jira] [Updated] (SOLR-8497) Merge Indexes doesn't close input directories on HDFS, causing HDFSLocalityReporter to log warnings once input directory is deleted.

[ https://issues.apache.org/jira/browse/SOLR-8497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-8497: -- Attachment: SOLR-8497.patch This should be the patch we need. > Merge Indexes doesn't close input

[jira] [Resolved] (SOLR-8575) Fix HDFSLogReader replay status numbers, a performance bug where we can reopen FSDataInputStream much too often, and an hdfs tlog data integrity bug.

[ https://issues.apache.org/jira/browse/SOLR-8575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-8575. --- Resolution: Fixed > Fix HDFSLogReader replay status numbers, a performance bug where we can > reopen

[jira] [Commented] (SOLR-8575) Fix HDFSLogReader replay status numbers, a performance bug where we can reopen FSDataInputStream much too often, and an hdfs tlog data integrity bug.

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

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155817#comment-15155817 ] Mark Miller commented on SOLR-8696: --- I'd love to get legacy mode out for 6, but I doubt I'll have the

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155815#comment-15155815 ] Mark Miller commented on SOLR-8696: --- bq. SliceMutator.addReplica Ah, got you sorry, check out:

[jira] [Updated] (LUCENE-7038) QueryScorer.init returns empty TokenStream if setMaxDocCharsToAnalyze is not previously called

[ https://issues.apache.org/jira/browse/LUCENE-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Stein updated LUCENE-7038: --- Description: This is a regression since Lucene 4.10 regarding The QueryScorer class in the

[jira] [Commented] (SOLR-7339) Upgrade Jetty from 9.2 to 9.3

[ https://issues.apache.org/jira/browse/SOLR-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155812#comment-15155812 ] Mark Miller commented on SOLR-7339: --- Just looked at the code on GitHub - looks like latest release does

[jira] [Commented] (SOLR-7339) Upgrade Jetty from 9.2 to 9.3

[ https://issues.apache.org/jira/browse/SOLR-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155805#comment-15155805 ] Mark Miller commented on SOLR-7339: --- Oh, good news. This is already fixed in master and perhaps in a

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5632/ Java: 64bit/jdk1.8.0_72 -XX:-UseCompressedOops -XX:+UseParallelGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.client.solrj.embedded.LargeVolumeJettyTest Error Message: ObjectTracker found 1 object(s)

Re: Removing branch_5x shortly

Yeah, please don't remove it. Let it be there. On Feb 21, 2016 01:02, "Uwe Schindler" wrote: > Hi, > > Let's keep the branch. The other ones from 3 and 4 are also still there. > > If anybody commits, who cares? If we don't release, it's just useless work. > > If we want to nuke

[jira] [Comment Edited] (SOLR-7339) Upgrade Jetty from 9.2 to 9.3

[ https://issues.apache.org/jira/browse/SOLR-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155784#comment-15155784 ] Mark Miller edited comment on SOLR-7339 at 2/20/16 10:40 PM: -

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.7.0_80) - Build # 15628 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15628/ Java: 64bit/jdk1.7.0_80 -XX:-UseCompressedOops -XX:+UseParallelGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.HttpPartitionTest Error Message: ObjectTracker found 1 object(s) that were not released!!!

[jira] [Comment Edited] (SOLR-7339) Upgrade Jetty from 9.2 to 9.3

[ https://issues.apache.org/jira/browse/SOLR-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155784#comment-15155784 ] Mark Miller edited comment on SOLR-7339 at 2/20/16 10:36 PM: -

[jira] [Commented] (SOLR-7339) Upgrade Jetty from 9.2 to 9.3

[ https://issues.apache.org/jira/browse/SOLR-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155784#comment-15155784 ] Mark Miller commented on SOLR-7339: --- [~gr...@webtide.com], [~joakime], looks like a default locale bug:

[JENKINS] Lucene-Solr-NightlyTests-trunk - Build # 939 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/939/ 1 tests failed. FAILED: org.apache.solr.cloud.hdfs.HdfsUnloadDistributedZkTest.test Error Message: Captured an uncaught exception in thread: Thread[id=48654, name=testExecutor-8080-thread-4, state=RUNNABLE,

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155773#comment-15155773 ] Mark Miller commented on SOLR-8696: --- bq. The only local changes I have are to comment out the calls to

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155772#comment-15155772 ] Mark Miller commented on SOLR-8696: --- I was on recent master at the time. I'll replicate and report steps

Re: Removing branch_5x shortly

> It sounds like one must assume git's gc is immediate, i.e. upon removing the > branch, any commits not reachable by any other "roots" would be deleted, even > if you "remembered" their specific commit hashes yourself. No, it isn't immediate. git tries hard to preserve your work in case you

Re: Removing branch_5x shortly

Not the norm is an understatement reading that issue :) - Mark On Sat, Feb 20, 2016 at 4:04 PM Anshum Gupta wrote: > Here's a similar question that came up during the 5.0 release. > >

Re: Removing branch_5x shortly

Here's a similar question that came up during the 5.0 release. https://issues.apache.org/jira/browse/LUCENE-5944?focusedCommentId=14138919=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14138919 The reply to this was convincing back then as 5.0 was released for different

Re: Removing branch_5x shortly

I think it fits a lot more with how we work to add some documentation to the release wiki and or elsewhere about changing index format after the next major release, and that the release manager should ping the list and scan changes for potential violations in such release situations. That seems

Re: Removing branch_5x shortly

On Sat, Feb 20, 2016 at 3:42 PM, Michael McCandless wrote: > But if we do that then the (already released) 6.0 won't be able to > read 5.6 indices, which I think would be very bad. For sure, forward compatibility would need to apply. That still leaves open a wide range

[jira] [Comment Edited] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155750#comment-15155750 ] Scott Blum edited comment on SOLR-8696 at 2/20/16 8:57 PM: --- What git sha are you

[jira] [Commented] (SOLR-8696) Optimize overseer + startup

[ https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155750#comment-15155750 ] Scott Blum commented on SOLR-8696: -- What git sha are you on? I'm absolutely not hitting that break point

Re: Removing branch_5x shortly

On Sat, Feb 20, 2016 at 1:32 PM, Yonik Seeley wrote: > On Sat, Feb 20, 2016 at 12:46 PM, Michael McCandless > wrote: >> We are precluding it: 5.5.x is the last feature release before 6.0.0. >> >> I don't think we should do another 5.x feature release

Re: Removing branch_5x shortly

On Sat, Feb 20, 2016 at 3:33 PM, Michael McCandless wrote: > I was simply going by what we did when we released 5.0, which was to > remove the 4.x branch (or rename it to 4.10.x maybe, but the net > effect is the same). I thought this was the practice for a major >

[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+105) - Build # 15937 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15937/ Java: 64bit/jdk-9-ea+105 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC -XX:-UseSuperWord 1 tests failed. FAILED: org.apache.solr.morphlines.solr.SolrMorphlineZkAliasTest.test Error Message: No live SolrServers available to

Re: Removing branch_5x shortly

I was simply going by what we did when we released 5.0, which was to remove the 4.x branch (or rename it to 4.10.x maybe, but the net effect is the same). I thought this was the practice for a major release. But it sounds like removing this branch in git is ... not a good idea technically. And

Re: Removing branch_5x shortly

bq. So what exactly was the old informal guidance that determined when branch_4x was removed>? Interesting, you are right. I don't recall that at all. There is probably a JIRA or email thread needle out there with the discussion. Silence and absence is consensus. I may even have been for the idea

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/415/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC 3 tests failed. FAILED: org.apache.solr.client.solrj.io.stream.StreamExpressionTest.testAll Error Message: Test abandoned because suite timeout was reached. Stack

Re: Removing branch_5x shortly

+1 for managing git branches the same way as branches were managed in svn (modulo any specific technical differences of git vs. svn). I see only branch_5x in svn right now - when in the staging of release 5.0 was branch_4x deleted? Looking at the official ReleaseToDo wiki, I don't actually see

Re: Removing branch_5x shortly

Hi, Let's keep the branch. The other ones from 3 and 4 are also still there. If anybody commits, who cares? If we don't release, it's just useless work. If we want to nuke branch, do the same for previous ones. Uwe Am 20. Februar 2016 19:58:21 MEZ, schrieb Dawid Weiss :

Re: Removing branch_5x shortly

> Can't we tag it and then delete the branch? Any reference. So yes, sure you can. But this doesn't really address the second part of my e-mail -- people would still have to issue: git remote prune origin and I don't want to fight Uwe over supposedly magical git commands :) > if infra let's us

Re: Removing branch_5x shortly

Can't we tag it and then delete the branch? I'm not a fan of removal as a way to prevent commits though. We should see if infra let's us put in any git hooks and protect branches from there. I'm not convinced we need a new strategy just because we are on git though. We generally don't decide we

Re: Removing branch_5x shortly

> git push origin --delete branch_5x > > (Instead of the crazy all-powerful-colon syntax). Ok. I don't think it's the right way to do it. > This just removes the "pointer" (branch_5x) to the latest commit hash > right? The commits unique to that branch still remain unless we ask > git to

[JENKINS] Lucene-Solr-5.5-Linux (32bit/jdk1.8.0_72) - Build # 55 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.5-Linux/55/ Java: 32bit/jdk1.8.0_72 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication Error Message: timed out waiting for collection1 startAt time to exceed: Sat Feb 20

Re: Removing branch_5x shortly

On Sat, Feb 20, 2016 at 12:46 PM, Michael McCandless wrote: > We are precluding it: 5.5.x is the last feature release before 6.0.0. > > I don't think we should do another 5.x feature release after 6.0.0 is out. Can't that be decided at some point in the future (i.e. if

Re: Removing branch_5x shortly

We are precluding it: 5.5.x is the last feature release before 6.0.0. I don't think we should do another 5.x feature release after 6.0.0 is out. Mike McCandless http://blog.mikemccandless.com On Sat, Feb 20, 2016 at 12:30 PM, Yonik Seeley wrote: > Why are we precluding a

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15936/ Java: 64bit/jdk1.8.0_72 -XX:-UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: org.apache.lucene.replicator.http.HttpReplicatorTest.testBasic Error Message: 127.0.0.1:46756 failed to respond Stack Trace:

Re: Removing branch_5x shortly

Why are we precluding a future 5.6 release (or are we)? -Yonik On Sat, Feb 20, 2016 at 11:52 AM, Michael McCandless wrote: > Please don't back-port anything to branch_5x: I'd like to remove it, > i.e. any back-ports from master should be only bug fixes and go to >

Re: Removing branch_5x shortly

Thanks for asking :) I was just going to do: git push origin --delete branch_5x (Instead of the crazy all-powerful-colon syntax). This just removes the "pointer" (branch_5x) to the latest commit hash right? The commits unique to that branch still remain unless we ask git to reclaim them?

Re: Removing branch_5x shortly

Before you do push anything can you explain or give the commands you plan to execute Mike? Deleting a branch is typically not a good idea that's why I ask. On Feb 20, 2016 17:52, "Michael McCandless" wrote: > Please don't back-port anything to branch_5x: I'd like to

Removing branch_5x shortly

Please don't back-port anything to branch_5x: I'd like to remove it, i.e. any back-ports from master should be only bug fixes and go to branch_5_5's next bug fix release (5.5.1) instead. I see some recent commits for Solr here ... if these are really bug-fixes, please re-push to 5.5 branch

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1684/ No tests ran. Build Log: [...truncated 29031 lines...] BUILD FAILED /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:756: The following error occurred while executing this line:

[jira] [Commented] (LUCENE-7039) Improve PointRangeQuery & co

[ https://issues.apache.org/jira/browse/LUCENE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155649#comment-15155649 ] Michael McCandless commented on LUCENE-7039: +1, I like this improvement, thanks [~rcmuir].

[jira] [Updated] (LUCENE-7039) Improve PointRangeQuery & co

[ https://issues.apache.org/jira/browse/LUCENE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-7039: Attachment: LUCENE-7039.patch Here is a prototype patch. > Improve PointRangeQuery & co >

[jira] [Created] (LUCENE-7039) Improve PointRangeQuery & co

Robert Muir created LUCENE-7039: --- Summary: Improve PointRangeQuery & co Key: LUCENE-7039 URL: https://issues.apache.org/jira/browse/LUCENE-7039 Project: Lucene - Core Issue Type: Task

[JENKINS] Lucene-Solr-5.5-Linux (32bit/jdk1.8.0_72) - Build # 53 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.5-Linux/53/ Java: 32bit/jdk1.8.0_72 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.core.TestNRTOpen.testSharedCores Error Message: expected:<3> but was:<2> Stack Trace: java.lang.AssertionError: expected:<3> but was:<2>

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

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1102/ 1 tests failed. FAILED: org.apache.solr.cloud.hdfs.HdfsCollectionsAPIDistributedZkTest.test Error Message: Captured an uncaught exception in thread: Thread[id=58380, name=collection4, state=RUNNABLE,

[jira] [Commented] (LUCENE-7033) ant prepare-release-no-sign fails intermittently

[ https://issues.apache.org/jira/browse/LUCENE-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155574#comment-15155574 ] Dawid Weiss commented on LUCENE-7033: - Jenkins configuration has been fixed to clean up before every

Re: git email format customizability: add branch to subject?

> "git: %(repo_name)s:%(shortbranch)s: %(subject)s" Looks good to me. I'd keep the repo name regardless of whether it's the main repo or not. Dawid On Sat, Feb 20, 2016 at 4:54 AM, Shawn Heisey wrote: > On 2/19/2016 6:04 PM, Ryan Ernst wrote: >> >> This sounds good, but

[JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.8.0_72) - Build # 5631 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5631/ Java: 64bit/jdk1.8.0_72 -XX:-UseCompressedOops -XX:+UseG1GC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.core.TestLazyCores Error Message: ObjectTracker found 4 object(s) that were not released!!!

[jira] [Commented] (LUCENE-6989) Implement MMapDirectory unmapping for coming Java 9 changes

[ https://issues.apache.org/jira/browse/LUCENE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155530#comment-15155530 ] Uwe Schindler commented on LUCENE-6989: --- Hi, I was able to reproduce the Hotspot bug and opened an

RE: [JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+105) - Build # 15928 - Failure!

Hi Rory, we found another bug in build 105 (but could have introduced much earlier, it is just new code in Lucene to allow us to handle the new MappedByteBuffer unmapping since build 105): Review ID: JI-9029693: Java 9 build 105 breaks MethodHandles calling interface methods This bug may

RE: [JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+105) - Build # 15928 - Failure!

Hi Rory, we found another bug in build 105 (but could have introduced much earlier, it is just new code in Lucene to allow us to handle the new MappedByteBuffer unmapping since build 105): Review ID: JI-9029693: Java 9 build 105 breaks MethodHandles calling interface methods This bug may