Re: Massive state-update bottleneck at scale

I talked about this type of thing with Jessica at Lucene / Sole revolution. One thing is, when you reconnect after connecting to ZK, it should now efficiently set every core as down in a single command, not each core. Beyond that, any single node knows how fast it's sending overseer updates. Each

Re: Massive state-update bottleneck at scale

Because that's how it works. On Wed, Nov 23, 2016 at 5:57 PM Walter Underwood wrote: > Why would other nodes need to see stale state? > > If they really need intermediate state changes, that sounds like a problem. > > wunder > Walter Underwood > wun...@wunderwood.org >

Re: Massive state-update bottleneck at scale

I didn't say stale state though actually. I said state progressions. On Wed, Nov 23, 2016 at 6:03 PM Mark Miller wrote: > Because that's how it works. > On Wed, Nov 23, 2016 at 5:57 PM Walter Underwood > wrote: > > Why would other nodes need to see

Re: Massive state-update bottleneck at scale

Although, if we fixed that the leader sometimes publishes state for replicas (which I think is a mistake, I worked hard initially to avoid a node ever publishing state for another node) you could at least track the last state Published and avoid repeating it over and over pretty easily. On Wed,

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/18357/ Java: 64bit/jdk-9-ea+140 -XX:-UseCompressedOops -XX:+UseG1GC 3 tests failed. FAILED: org.apache.lucene.index.TestIndexSorting.testStringAlreadySorted Error Message: this writer hit an unrecoverable error; cannot commit

Re: Massive state-update bottleneck at scale

Why would other nodes need to see stale state? If they really need intermediate state changes, that sounds like a problem. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 23, 2016, at 2:53 PM, Mark Miller wrote: > > In

[jira] [Updated] (SOLR-6606) In cloud mode the leader should distribute autoCommits to it's replicas

[ https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-6606: --- Attachment: SOLR-6606.patch Updated patch for this issue. This patch updated to lastest source and

Massive state-update bottleneck at scale

I've been fighting fires the last day where certain of our solr nodes will have a long GC pauses that cause them to lose their ZK connection and have to reconnect. That would be annoying, but survivable, although obvious it's something I want to fix. But what makes it fatal is the current design

[jira] [Commented] (SOLR-7036) Faster method for group.facet

[ https://issues.apache.org/jira/browse/SOLR-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691534#comment-15691534 ] Jim Musil commented on SOLR-7036: - Erick, I'm not sure I'm qualified to make a call on this, but from my

[jira] [Commented] (SOLR-9708) Expose UnifiedHighlighter in Solr

[ https://issues.apache.org/jira/browse/SOLR-9708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691807#comment-15691807 ] Timothy M. Rodriguez commented on SOLR-9708: Looks great! Adding the other highlighters to

Re: Massive state-update bottleneck at scale

In many cases other nodes need to see a progression of state changes. You really have to clear the deck and try to start from 0. On Wed, Nov 23, 2016 at 5:50 PM Walter Underwood wrote: > If the queue is local and the state messages are complete, the local queue > should

[JENKINS] Lucene-Solr-6.x-Windows (32bit/jdk1.8.0_102) - Build # 577 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Windows/577/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.handler.admin.CoreAdminHandlerTest.testDeleteInstanceDirAfterCreateFailure Error Message: The data directory was not cleaned up on

Re: Massive state-update bottleneck at scale

If the queue is local and the state messages are complete, the local queue should only send the latest, most accurate update. The rest can be skipped. The same could be done on the receiving end. Suck the queue dry, then choose the most recent. If the updates depend on previous updates, it

[jira] [Commented] (SOLR-7036) Faster method for group.facet

[ https://issues.apache.org/jira/browse/SOLR-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691507#comment-15691507 ] Erick Erickson commented on SOLR-7036: -- I'm thoroughly confused about the state of these two JIRAs,

Re: Massive state-update bottleneck at scale

Yes, publishing state for other nodes seems like a problem waiting to happen. Let Zookeeper be the single source of truth and live with the extra traffic. How about a first change to ignore any second-hand state, then later we can stop sending it and collapse the queues. Maybe receiving queues

Re: Massive state-update bottleneck at scale

The second thing I want to look at doing is replacing queued state update operations with local CAS loops for state format v2 collections, with in-process collection-level mutex to ensure that a node isn't contending with itself. This would only be for state updates, anything more complex would

Re: Massive state-update bottleneck at scale

On Wed, Nov 23, 2016 at 5:45 PM, Mark Miller wrote: > One thing is, when you reconnect after connecting to ZK, it should now > efficiently set every core as down in a single command, not each core. Yeah, I backported downnode, but it still actually takes a long time for

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/18358/ Java: 32bit/jdk-9-ea+140 -server -XX:+UseG1GC 1 tests failed. FAILED: org.apache.lucene.search.join.TestJoinUtil.testSingleValueRandomJoin Error Message: expected: but

[jira] [Updated] (SOLR-9718) All JUnits of Streaming use java assert to compare double should use assertEquals()

[ https://issues.apache.org/jira/browse/SOLR-9718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-9718: - Issue Type: Task (was: Sub-task) Parent: (was: SOLR-9636) > All JUnits of Streaming use java

[jira] [Resolved] (SOLR-9717) /export should support other formats

[ https://issues.apache.org/jira/browse/SOLR-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9717. -- Resolution: Fixed Fix Version/s: 6.4 master (7.0) > /export should support

[JENKINS] Lucene-Solr-master-Windows (32bit/jdk1.8.0_102) - Build # 6242 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6242/ Java: 32bit/jdk1.8.0_102 -server -XX:+UseParallelGC 2 tests failed. FAILED: org.apache.solr.cloud.TestSolrCloudWithDelegationTokens.testDelegationTokenCancelFail Error Message: expected:<200> but was:<404> Stack Trace:

[jira] [Resolved] (SOLR-9734) wt=javabin support at /export

[ https://issues.apache.org/jira/browse/SOLR-9734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9734. -- Resolution: Duplicate Fix Version/s: 6.4 master (7.0) > wt=javabin support at

[jira] [Updated] (SOLR-9721) Create a javabin parser for streaming end point

[ https://issues.apache.org/jira/browse/SOLR-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-9721: - Fix Version/s: master (7.0) > Create a javabin parser for streaming end point >

[jira] [Closed] (SOLR-9626) Admin UI (new) does not include highlighting indicating match in Analysis View

[ https://issues.apache.org/jira/browse/SOLR-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandre Rafalovitch closed SOLR-9626. --- > Admin UI (new) does not include highlighting indicating match in Analysis View >

[jira] [Created] (SOLR-9798) The type FacetDoubleMerger is already defined Error in FacetModule class

adeppa created SOLR-9798: Summary: The type FacetDoubleMerger is already defined Error in FacetModule class Key: SOLR-9798 URL: https://issues.apache.org/jira/browse/SOLR-9798 Project: Solr Issue

[jira] [Updated] (SOLR-9708) Expose UnifiedHighlighter in Solr

[ https://issues.apache.org/jira/browse/SOLR-9708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated SOLR-9708: --- Attachment: SOLR-9708.patch Here's the patch, with FASTVECTOR -> FAST_VECTOR. Proposed CHANGES.txt

[JENKINS-EA] Lucene-Solr-6.x-Linux (32bit/jdk-9-ea+140) - Build # 2255 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/2255/ Java: 32bit/jdk-9-ea+140 -server -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.handler.dataimport.TestBuiltInEvaluators.testDateFormatEvaluator Error Message: expected:<2016-11-22 0[0]> but was:<2016-11-22 0[1]>

[jira] [Assigned] (SOLR-9512) CloudSolrClient's cluster state cache can break direct updates to leaders

[ https://issues.apache.org/jira/browse/SOLR-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-9512: Assignee: Noble Paul > CloudSolrClient's cluster state cache can break direct updates to leaders >

[jira] [Resolved] (SOLR-9636) Add support for javabin for /stream, /sql internode communication

[ https://issues.apache.org/jira/browse/SOLR-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9636. -- Resolution: Fixed Fix Version/s: 6.4 master (7.0) > Add support for javabin

[jira] [Updated] (SOLR-9636) Add support for javabin for /stream, /sql internode communication

[ https://issues.apache.org/jira/browse/SOLR-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-9636: - Summary: Add support for javabin for /stream, /sql internode communication (was: Use javabin for /stream,

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/966/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestMiniSolrCloudClusterSSL Error Message: 1 thread leaked from SUITE scope at

[jira] [Commented] (SOLR-9721) Create a javabin parser for streaming end point

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

[jira] [Commented] (SOLR-9721) Create a javabin parser for streaming end point

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

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/18359/ Java: 64bit/jdk1.8.0_102 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestSolrCloudWithSecureImpersonation Error Message: 4 threads leaked from SUITE

[jira] [Created] (SOLR-9797) Admin UI not opening/working

adeppa created SOLR-9797: Summary: Admin UI not opening/working Key: SOLR-9797 URL: https://issues.apache.org/jira/browse/SOLR-9797 Project: Solr Issue Type: Bug Security Level: Public

[jira] [Updated] (SOLR-9797) Admin UI not opening/working

[ https://issues.apache.org/jira/browse/SOLR-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] adeppa updated SOLR-9797: - Attachment: Screen Shot 2016-11-24 at 12.53.29 PM.png Screen Shot 2016-11-24 at 12.37.25 PM.png >

[jira] [Resolved] (SOLR-9721) Create a javabin parser for streaming end point

[ https://issues.apache.org/jira/browse/SOLR-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9721. -- Resolution: Fixed Fix Version/s: 6.4 > Create a javabin parser for streaming end point >

Re: Future of FieldCache in Solr

On Wed, 2016-10-26 at 13:05 +, Adrien Grand wrote: > But we seem to still care a lot about uninverting, which does > not make sense to me since everybody should have moved to doc values > already? I might have missed something here, but doesn't such a switch mean that it will no longer be

[jira] [Commented] (LUCENE-7543) Make changes-to-html target an offline operation

[ https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689770#comment-15689770 ] Alexandre Rafalovitch commented on LUCENE-7543: --- bq. I tried to write -0 but I couldn't

[jira] [Commented] (LUCENE-7521) Simplify PackedInts

[ https://issues.apache.org/jira/browse/LUCENE-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689447#comment-15689447 ] Toke Eskildsen commented on LUCENE-7521: I was involved in the original PackedInts

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6240/ Java: 64bit/jdk1.8.0_102 -XX:-UseCompressedOops -XX:+UseParallelGC 2 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication Error Message: expected:<1> but was:<0> Stack

[JENKINS] Lucene-Solr-NightlyTests-master - Build # 1161 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1161/ 9 tests failed. FAILED: org.apache.solr.cloud.CdcrReplicationDistributedZkTest.testTargetCollectionNotAvailable Error Message: Timeout while trying to assert replication errors Stack Trace: java.lang.AssertionError:

[jira] [Reopened] (SOLR-9751) PreAnalyzedField can cause managed schema corruption

[ https://issues.apache.org/jira/browse/SOLR-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe reopened SOLR-9751: -- The test I added on this issue has been failing regularly, e.g. from

[JENKINS] Lucene-Solr-6.x-Windows (32bit/jdk1.8.0_102) - Build # 576 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Windows/576/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.handler.admin.CoreAdminHandlerTest.testDeleteInstanceDirAfterCreateFailure Error Message: The data directory was not cleaned up on

[jira] [Comment Edited] (SOLR-9616) Solr throws exception when expand=true on empty result

[ https://issues.apache.org/jira/browse/SOLR-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689995#comment-15689995 ] Timo Hund edited comment on SOLR-9616 at 11/23/16 12:39 PM: [~joel.bernstein]

[jira] [Commented] (SOLR-9616) Solr throws exception when expand=true on empty result

[ https://issues.apache.org/jira/browse/SOLR-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689995#comment-15689995 ] Timo Hund commented on SOLR-9616: - [~joel.bernstein] Is there anything i can do to help? This issue might

[jira] [Commented] (LUCENE-7521) Simplify PackedInts

[ https://issues.apache.org/jira/browse/LUCENE-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690132#comment-15690132 ] Adrien Grand commented on LUCENE-7521: -- Thanks Toke for pointing to these benchmarks. I agree the

[jira] [Commented] (SOLR-9728) Ability to specify Key Store type in solr.in file for SSL

[ https://issues.apache.org/jira/browse/SOLR-9728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690110#comment-15690110 ] Michael Suzuki commented on SOLR-9728: -- [~risdenk] Tried and tested the patch, it works for me. >

[jira] [Assigned] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-7569: -- Assignee: Michael McCandless > TestIndexSorting.testRandom3() failures >

[jira] [Updated] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-7569: --- Fix Version/s: master (7.0) 6.4.0 >

[jira] [Updated] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-7569: --- Priority: Blocker (was: Major) > TestIndexSorting.testRandom3() failures >

Re: Future of FieldCache in Solr

This is supported at the Lucene level via SortedSetDocValues. Solr doesn't yet support this for its TextField -- https://issues.apache.org/jira/browse/SOLR-8362 however you could work around this with an URP or copyField or perhaps subclassing TextField so that you can tokenize the text a

[jira] [Commented] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689969#comment-15689969 ] Michael McCandless commented on LUCENE-7569: This looks like bad ... I think we need to fix

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3664/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication Error Message: expected:<1> but was:<0> Stack Trace:

[jira] [Comment Edited] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690240#comment-15690240 ] Kelvin Wong edited comment on SOLR-8785 at 11/23/16 2:28 PM: - Thanks Shalin,

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690240#comment-15690240 ] Kelvin Wong commented on SOLR-8785: --- Thanks Shalin, Jeff, and Christine! One problem I noticed is that

[jira] [Commented] (LUCENE-7543) Make changes-to-html target an offline operation

[ https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690364#comment-15690364 ] Alexandre Rafalovitch commented on LUCENE-7543: --- Sorry. You can stay at -1 :-) I do not see

[jira] [Created] (SOLR-9796) Adding custom headers in UpdateRequest while sending to Solr Server

Devanshi created SOLR-9796: -- Summary: Adding custom headers in UpdateRequest while sending to Solr Server Key: SOLR-9796 URL: https://issues.apache.org/jira/browse/SOLR-9796 Project: Solr Issue

[jira] [Created] (LUCENE-7572) Cache the hashcode of the doc values terms queries

Adrien Grand created LUCENE-7572: Summary: Cache the hashcode of the doc values terms queries Key: LUCENE-7572 URL: https://issues.apache.org/jira/browse/LUCENE-7572 Project: Lucene - Core

[jira] [Updated] (SOLR-9796) Adding custom headers in UpdateRequest while sending to Solr Server

[ https://issues.apache.org/jira/browse/SOLR-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devanshi updated SOLR-9796: --- Description: We have created an custom authentication plugin, which takes certain header parameters.

[jira] [Commented] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690321#comment-15690321 ] Steve Rowe commented on LUCENE-7569: Two more reproducing master failures this morning on my Jenkins

[jira] [Updated] (LUCENE-7572) Cache the hashcode of the doc values terms queries

[ https://issues.apache.org/jira/browse/LUCENE-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-7572: - Attachment: LUCENE-7572.patch Here is a patch. DocValuesTermsQuery and DocValuesNumbersQuery now

[jira] [Commented] (LUCENE-7521) Simplify PackedInts

[ https://issues.apache.org/jira/browse/LUCENE-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690275#comment-15690275 ] Yonik Seeley commented on LUCENE-7521: -- The rational for this patch looked to be "most

[jira] [Commented] (LUCENE-7543) Make changes-to-html target an offline operation

[ https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690273#comment-15690273 ] Steve Rowe commented on LUCENE-7543: bq. My understanding is that doap file is for tools. I agree,

[jira] [Commented] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690323#comment-15690323 ] Steve Rowe commented on LUCENE-7569: Two more reproducing master failures this morning on my Jenkins

[jira] [Commented] (LUCENE-7543) Make changes-to-html target an offline operation

[ https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690409#comment-15690409 ] Steve Rowe commented on LUCENE-7543: I guess the essense of our disagreement is whether additional

[jira] [Commented] (LUCENE-7569) TestIndexSorting.testRandom3() failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690219#comment-15690219 ] Ferenczi Jim commented on LUCENE-7569: -- I am looking at it. Seems like a bug when sorting

[jira] [Updated] (SOLR-9796) Adding custom headers in UpdateRequest while sending to Solr Server

[ https://issues.apache.org/jira/browse/SOLR-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devanshi updated SOLR-9796: --- Description: We have created an custom authentication plugin, which takes certain header parameters.

[jira] [Updated] (LUCENE-7569) TestIndexSorting failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-7569: --- Summary: TestIndexSorting failures (was: TestIndexSorting.testRandom3() failures) >

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/965/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.hdfs.HdfsRecoveryZkTest Error Message: ObjectTracker found 1 object(s) that were not

[jira] [Commented] (SOLR-9787) Replace json.nl=arrnvp with json.nl=arrntv (array of Name Type Value) style in JSONResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-9787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690715#comment-15690715 ] Jonny Marks commented on SOLR-9787: --- I plan to work on this in the first half of December > Replace

[JENKINS] Lucene-Solr-NightlyTests-6.x - Build # 208 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/208/ 6 tests failed. FAILED: org.apache.solr.cloud.CdcrReplicationDistributedZkTest.testResilienceWithDeleteByQueryOnTarget Error Message: Timeout while trying to assert number of documents @ target_collection Stack Trace:

[jira] [Reopened] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar reopened SOLR-8785: - Thanks Kelvin, I'll fix. > Use Metrics library for core metrics >

[jira] [Updated] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-8785: Attachment: SOLR_8775_rates_per_minute_fix.patch I think we should keep our per

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690859#comment-15690859 ] Kelvin Wong commented on SOLR-8785: --- I think the RequestHandlerBase and AnalyticsStatisticsCollector

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

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

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

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

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

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

[jira] [Resolved] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-8785. - Resolution: Fixed Thanks for the review, Kelvin! > Use Metrics library for core

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

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

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690864#comment-15690864 ] Shalin Shekhar Mangar commented on SOLR-8785: - Ah, I was too eager to commit. You are right, I

[jira] [Commented] (LUCENE-7564) AnalyzingInfixSuggester should close its IndexWriter by default at the end of build()

[ https://issues.apache.org/jira/browse/LUCENE-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690933#comment-15690933 ] Steve Rowe commented on LUCENE-7564: My Jenkins found a non-reproducing master seed for a

[jira] [Commented] (SOLR-8785) Use Metrics library for core metrics

[ https://issues.apache.org/jira/browse/SOLR-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691044#comment-15691044 ] Kelvin Wong commented on SOLR-8785: --- No problem! Great to see this resolved. > Use Metrics library for

[JENKINS] Lucene-Solr-6.x-Linux (32bit/jdk1.8.0_102) - Build # 2251 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/2251/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestSolrCloudWithSecureImpersonation Error Message: 2 threads leaked from SUITE scope at

[jira] [Commented] (LUCENE-7569) TestIndexSorting failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691080#comment-15691080 ] Steve Rowe commented on LUCENE-7569: This comment somehow got added twice to the issue, so I deleted

[jira] [Commented] (SOLR-4735) Improve Solr metrics reporting

[ https://issues.apache.org/jira/browse/SOLR-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690992#comment-15690992 ] Jeff Wartes commented on SOLR-4735: --- For what it's worth, this looks like really great stuff to me. I'm

[jira] [Commented] (LUCENE-7569) TestIndexSorting failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691060#comment-15691060 ] Ferenczi Jim commented on LUCENE-7569: -- Thanks [~sar...@syr.edu]. We've investigated this with

[jira] [Issue Comment Deleted] (LUCENE-7569) TestIndexSorting failures

[ https://issues.apache.org/jira/browse/LUCENE-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated LUCENE-7569: --- Comment: was deleted (was: Two more reproducing master failures this morning on my Jenkins - yet

[JENKINS] Lucene-Solr-Tests-master - Build # 1495 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1495/ 2 tests failed. FAILED: org.apache.lucene.index.TestIndexSorting.testMultiValuedStringAlreadySorted Error Message: background merge hit exception: _n(7.0.0):c111:[indexSort= selector=MIN,] into _o [maxNumSegments=1] Stack

[jira] [Commented] (SOLR-9788) Use instrumented jetty classes

[ https://issues.apache.org/jira/browse/SOLR-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691300#comment-15691300 ] Shalin Shekhar Mangar commented on SOLR-9788: - Here's an example output from /admin/metrics:

[JENKINS] Lucene-Solr-master-Windows (32bit/jdk1.8.0_102) - Build # 6241 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6241/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.handler.admin.CoreAdminHandlerTest.testDeleteInstanceDirAfterCreateFailure Error Message: The data directory was not cleaned up on

[jira] [Commented] (LUCENE-7521) Simplify PackedInts

[ https://issues.apache.org/jira/browse/LUCENE-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691118#comment-15691118 ] Toke Eskildsen commented on LUCENE-7521: Just to be clear, I was only talking about the bit

[jira] [Updated] (SOLR-9788) Use instrumented jetty classes

[ https://issues.apache.org/jira/browse/SOLR-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-9788: Attachment: SOLR_9788.patch Changes: * The metric registery is renamed to "solr"

[JENKINS-EA] Lucene-Solr-6.x-Linux (32bit/jdk-9-ea+140) - Build # 2252 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/2252/ Java: 32bit/jdk-9-ea+140 -server -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.handler.component.SpellCheckComponentTest.test Error Message: List size mismatch @ spellcheck/suggestions Stack Trace: