[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_121) - Build # 19205 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19205/ Java: 32bit/jdk1.8.0_121 -client -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.OnlyLeaderIndexesTest.test Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931560#comment-15931560 ] Mark Miller commented on SOLR-10265: The main reason a zk queue was used instead of in memory was that

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931544#comment-15931544 ] Erick Erickson commented on SOLR-10265: --- bq: My suspicion is that it's problematic because of the

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931532#comment-15931532 ] Shawn Heisey commented on SOLR-10265: - bq. We should seriously reconsider the idea of using ZK queue

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 1203 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1203/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.core.TestDynamicLoading.testDynamicLoading Error Message: Could not get expected value 'X val' for path 'x' full output: {

[JENKINS] Lucene-Solr-Tests-6.x - Build # 805 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/805/ 1 tests failed. FAILED: org.apache.solr.cloud.MissingSegmentRecoveryTest.testLeaderRecovery Error Message: Expected a collection with one shard and two replicas null Last available state:

[JENKINS] Lucene-Solr-6.x-MacOSX (64bit/jdk1.8.0) - Build # 769 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-MacOSX/769/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.CustomCollectionTest.testCustomCollectionsAPI Error Message: Could not find collection : implicitcoll Stack Trace:

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931501#comment-15931501 ] Noble Paul commented on SOLR-10265: --- Order of events between two clients don't matter > Overseer can

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931500#comment-15931500 ] Erick Erickson commented on SOLR-10265: --- bq: The client should take care of the ordering. The case

[JENKINS-EA] Lucene-Solr-master-Linux (32bit/jdk-9-ea+160) - Build # 19203 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19203/ Java: 32bit/jdk-9-ea+160 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.OnlyLeaderIndexesTest.test Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931437#comment-15931437 ] Noble Paul commented on SOLR-10265: --- bq.Depending on the timing of the retry logic, the clients could

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3904 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3904/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 6 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testCollectionsAPI Error Message: Error from server at

[jira] [Resolved] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-10315. -- Resolution: Not A Problem So I think we can safely resolve this as it's not a problem anymore

[jira] [Commented] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931392#comment-15931392 ] Rohit commented on SOLR-10315: -- Hi Varun, The issue is only in the 5X branch not in 6x. The CSS file which

[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_121) - Build # 19202 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19202/ Java: 32bit/jdk1.8.0_121 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.OnlyLeaderIndexesTest.test Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Resolved] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

[ https://issues.apache.org/jira/browse/LUCENE-7748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe resolved LUCENE-7748. Resolution: Fixed Assignee: Steve Rowe Fix Version/s: 6.4.3

Re: [JENKINS] Lucene-Solr-6.x-Windows (64bit/jdk1.8.0_121) - Build # 786 - Still Unstable!

I *think* I fixed this one... we'll see if anything else comes up. Frustratingly I can't reproduce anything but I'm in the process of getting a Windows VM for the purposes of reproducing test failures. On Fri, Mar 17, 2017 at 6:43 PM Policeman Jenkins Server < jenk...@thetaphi.de> wrote: >

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

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

[jira] [Commented] (SOLR-10265) Overseer can become the bottleneck in very large clusters

[ https://issues.apache.org/jira/browse/SOLR-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931336#comment-15931336 ] Erick Erickson commented on SOLR-10265: --- [~noble.paul] Interesting. You're essentially replacing the

[jira] [Commented] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931333#comment-15931333 ] Varun Thacker commented on SOLR-10315: -- Hi Rohit, I tried reproducing this on Solr 6.4.2 and I

[jira] [Updated] (LUCENE-7748) buildAndPushRelease.py should fail if the project DOAP files are missing releases that are less than the release being produced

[ https://issues.apache.org/jira/browse/LUCENE-7748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-7748: --- Attachment: LUCENE-7748.patch Slightly modified patch, to report all collected errors on both DOAP

[jira] [Updated] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated SOLR-10315: - Affects Version/s: 5.0 > Core selector fixed width drop-down truncates core names in UI >

[jira] [Updated] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated SOLR-10315: - Labels: AdminUI CoreSelector_DropdownMenu (was: ) > Core selector fixed width drop-down truncates core names in

[jira] [Commented] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931328#comment-15931328 ] Rohit commented on SOLR-10315: -- Hi Alexandre, Yes we can achieve this with a minor modification of CSS. You

[jira] [Issue Comment Deleted] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated SOLR-10315: - Comment: was deleted (was: The Core Selector Menu after CSS modification ) > Core selector fixed width drop-down

[jira] [Updated] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated SOLR-10315: - Attachment: Menu_after_css_chnage.png The Core Selector Menu after CSS modification > Core selector fixed width

[jira] [Updated] (SOLR-10315) Core selector fixed width drop-down truncates core names in UI

[ https://issues.apache.org/jira/browse/SOLR-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit updated SOLR-10315: - Attachment: SOLR-10315.patch > Core selector fixed width drop-down truncates core names in UI >

[JENKINS] Lucene-Solr-Tests-6.x - Build # 803 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/803/ 1 tests failed. FAILED: org.apache.solr.cloud.MissingSegmentRecoveryTest.testLeaderRecovery Error Message: Expected a collection with one shard and two replicas null Last available state:

[JENKINS] Lucene-Solr-6.x-Solaris (64bit/jdk1.8.0) - Build # 735 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Solaris/735/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testCollectionReload Error Message: Error from server at https://127.0.0.1:47728/solr:

[jira] [Resolved] (LUCENE-7738) Add new InetAddressRangeField

[ https://issues.apache.org/jira/browse/LUCENE-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Knize resolved LUCENE-7738. Resolution: Implemented > Add new InetAddressRangeField > - >

[jira] [Comment Edited] (SOLR-10295) Decide online location for Ref Guide HTML pages

[ https://issues.apache.org/jira/browse/SOLR-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931258#comment-15931258 ] Shawn Heisey edited comment on SOLR-10295 at 3/18/17 4:05 PM: -- bq. Define

[jira] [Commented] (SOLR-10295) Decide online location for Ref Guide HTML pages

[ https://issues.apache.org/jira/browse/SOLR-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931258#comment-15931258 ] Shawn Heisey commented on SOLR-10295: - bq. Define only the PDF as the official guide release. The

[jira] [Commented] (SOLR-10294) Decide branching strategy for Ref Guide

[ https://issues.apache.org/jira/browse/SOLR-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931255#comment-15931255 ] Steve Rowe commented on SOLR-10294: --- +1 for #1. > Decide branching strategy for Ref Guide >

[jira] [Commented] (SOLR-10295) Decide online location for Ref Guide HTML pages

[ https://issues.apache.org/jira/browse/SOLR-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931251#comment-15931251 ] Steve Rowe commented on SOLR-10295: --- bq. Maybe we could leverage 1)'s output and bless a particular

[jira] [Commented] (SOLR-10295) Decide online location for Ref Guide HTML pages

[ https://issues.apache.org/jira/browse/SOLR-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931248#comment-15931248 ] Steve Rowe commented on SOLR-10295: --- bq. Maybe the "this is for unreleased version of the Solr" is

[JENKINS-EA] Lucene-Solr-master-Linux (64bit/jdk-9-ea+160) - Build # 19200 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19200/ Java: 64bit/jdk-9-ea+160 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.OnlyLeaderIndexesTest.test Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Commented] (SOLR-10286) Declare a field as "large", don't keep value in the document cache

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

[jira] [Commented] (LUCENE-7738) Add new InetAddressRangeField

[ https://issues.apache.org/jira/browse/LUCENE-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931235#comment-15931235 ] Erick Erickson commented on LUCENE-7738: This has been committed, can it be closed? > Add new

[jira] [Commented] (SOLR-10286) Declare a field as "large", don't keep value in the document cache

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

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3903 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3903/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.core.snapshots.TestSolrCloudSnapshots.testSnapshots Error Message: Collection not found: SolrCloudSnapshots Stack Trace:

[JENKINS] Lucene-Solr-6.x-Windows (64bit/jdk1.8.0_121) - Build # 787 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Windows/787/ Java: 64bit/jdk1.8.0_121 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.search.LargeFieldTest Error Message: Illegal char at index 17: ignoredSchemaName? Stack

[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_121) - Build # 19198 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19198/ Java: 32bit/jdk1.8.0_121 -server -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.TestCloudRecovery.leaderRecoverFromLogOnStartupTest Error Message: expected:<4> but was:<2> Stack Trace:

[JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_121) - Build # 6457 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6457/ Java: 64bit/jdk1.8.0_121 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.search.LargeFieldTest Error Message: Illegal char at index 17: ignoredSchemaName? Stack

[jira] [Assigned] (SOLR-10079) TestInPlaceUpdates(Distrib|Standalone) failures

[ https://issues.apache.org/jira/browse/SOLR-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Chattopadhyaya reassigned SOLR-10079: --- Assignee: Cao Manh Dat (was: Ishan Chattopadhyaya) >

[jira] [Reopened] (SOLR-10079) TestInPlaceUpdates(Distrib|Standalone) failures

[ https://issues.apache.org/jira/browse/SOLR-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Chattopadhyaya reopened SOLR-10079: - Re-opening due to new failures after SOLR-9835 merge. >

[jira] [Commented] (SOLR-10079) TestInPlaceUpdates(Distrib|Standalone) failures

[ https://issues.apache.org/jira/browse/SOLR-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931112#comment-15931112 ] Ishan Chattopadhyaya commented on SOLR-10079: - Few observations on these failures: # Ever

[jira] [Comment Edited] (SOLR-10079) TestInPlaceUpdates(Distrib|Standalone) failures

[ https://issues.apache.org/jira/browse/SOLR-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1593#comment-1593 ] Ishan Chattopadhyaya edited comment on SOLR-10079 at 3/18/17 7:43 AM: --

[jira] [Commented] (SOLR-10079) TestInPlaceUpdates(Distrib|Standalone) failures

[ https://issues.apache.org/jira/browse/SOLR-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1593#comment-1593 ] Ishan Chattopadhyaya commented on SOLR-10079: - Another similar failure: {code} Build:

[jira] [Updated] (SOLR-10316) Unloading a core can remove a ZK SolrCore registration entry for the wrong SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-10316: --- Attachment: SOLR-10316.patch Here is a patch that tries to match baseUrl on core unload. > Unloading

[jira] [Updated] (SOLR-10316) Unloading a core can remove a ZK SolrCore registration entry for the wrong SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-10316: --- Attachment: (was: SOLR-10316.patch) > Unloading a core can remove a ZK SolrCore registration

[jira] [Commented] (SOLR-10316) Unloading a core can remove a ZK SolrCore registration entry for the wrong SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931088#comment-15931088 ] Mark Miller commented on SOLR-10316: Patch is off. Was in the weeds a bit. The extra info we need to

[jira] [Updated] (SOLR-10316) Unloading a core can remove a ZK SolrCore registration entry for the wrong SolrCore.

[ https://issues.apache.org/jira/browse/SOLR-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-10316: --- Description: We only use core node name and collection to match in ZK#unregister(core). This means