Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] IndexStatsIT.testConcurrentIndexingAndStatsRequests failure in 7.6 #52406

Closed
astefan opened this issue Feb 17, 2020 · 3 comments · Fixed by #52581
Closed

[CI] IndexStatsIT.testConcurrentIndexingAndStatsRequests failure in 7.6 #52406

astefan opened this issue Feb 17, 2020 · 3 comments · Fixed by #52581
Labels
:Data Management/Stats Statistics tracking and retrieval APIs >test-failure Triaged test failures from CI

Comments

@astefan
Copy link
Contributor

astefan commented Feb 17, 2020

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.6+multijob-unix-compatibility/os=debian-9&&immutable/65/console

01:43:58 org.elasticsearch.indices.stats.IndexStatsIT > testConcurrentIndexingAndStatsRequests FAILED
01:43:58     java.lang.AssertionError: 
01:43:58     Expected: an empty collection
01:43:58          but: <[[test][7] failed, reason [FailedNodeException[Failed node [QSoO4D6ZQ56SM8kqibBAkg]]; nested: RemoteTransportException[[node_s1][127.0.0.1:37625][indices:monitor/stats[n]]]; nested: IllegalStateException[Negative longs unsupported, use writeLong or writeZLong for negative numbers [-1]]; ], [test][5] failed, reason [FailedNodeException[Failed node [QSoO4D6ZQ56SM8kqibBAkg]]; nested: RemoteTransportException[[node_s1][127.0.0.1:37625][indices:monitor/stats[n]]]; nested: IllegalStateException[Negative longs unsupported, use writeLong or writeZLong for negative numbers [-1]]; ], [test][9] failed, reason [FailedNodeException[Failed node [QSoO4D6ZQ56SM8kqibBAkg]]; nested: RemoteTransportException[[node_s1][127.0.0.1:37625][indices:monitor/stats[n]]]; nested: IllegalStateException[Negative longs unsupported, use writeLong or writeZLong for negative numbers [-1]]; ], [test][3] failed, reason [FailedNodeException[Failed node [QSoO4D6ZQ56SM8kqibBAkg]]; nested: RemoteTransportException[[node_s1][127.0.0.1:37625][indices:monitor/stats[n]]]; nested: IllegalStateException[Negative longs unsupported, use writeLong or writeZLong for negative numbers [-1]]; ], [test][1] failed, reason [FailedNodeException[Failed node [QSoO4D6ZQ56SM8kqibBAkg]]; nested: RemoteTransportException[[node_s1][127.0.0.1:37625][indices:monitor/stats[n]]]; nested: IllegalStateException[Negative longs unsupported, use writeLong or writeZLong for negative numbers [-1]]; ]]>
01:43:58         at __randomizedtesting.SeedInfo.seed([72478EA70ABABFF9:C5D6E56E887CA8C7]:0)
01:43:58         at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
01:43:58         at org.junit.Assert.assertThat(Assert.java:956)
01:43:58         at org.junit.Assert.assertThat(Assert.java:923)
01:43:58         at org.elasticsearch.indices.stats.IndexStatsIT.testConcurrentIndexingAndStatsRequests(IndexStatsIT.java:1206)
01:43:58 REPRODUCE WITH: ./gradlew ':server:integTest' --tests "org.elasticsearch.indices.stats.IndexStatsIT.testConcurrentIndexingAndStatsRequests" -Dtests.seed=72478EA70ABABFF9 -Dtests.security.manager=true -Dtests.locale=sr-Latn-BA -Dtests.timezone=BET -Dcompiler.java=13

I am not 100% sure this is a true failure, since in the test that ran after this one there is a failing node, but at the same time the error itself in the testConcurrentIndexingAndStatsRequests test doesn't have a root exception related to the node failure:

01:43:58   1> [2020-02-16T19:43:57,992][INFO ][o.e.c.c.Coordinator      ] [node_s1] master node [{node_s0}{lf2hdgwfShOQpBcXhvQ8mQ}{EkQzmawFRDeKE7Na-uro4Q}{127.0.0.1}{127.0.0.1:40999}{dim}] failed, restarting discovery
01:43:58   1> org.elasticsearch.transport.NodeDisconnectedException: [node_s0][127.0.0.1:40999][disconnected] disconnected
01:43:58   1> [2020-02-16T19:43:57,993][INFO ][o.e.c.s.ClusterApplierService] [node_s1] master node changed {previous [{node_s0}{lf2hdgwfShOQpBcXhvQ8mQ}{EkQzmawFRDeKE7Na-uro4Q}{127.0.0.1}{127.0.0.1:40999}{dim}], current []}, term: 1, version: 164, reason: becoming candidate: onLeaderFailure
01:43:58   1> [2020-02-16T19:43:57,996][WARN ][o.e.c.NodeConnectionsService] [node_s1] failed to connect to {node_s0}{lf2hdgwfShOQpBcXhvQ8mQ}{EkQzmawFRDeKE7Na-uro4Q}{127.0.0.1}{127.0.0.1:40999}{dim} (tried [1] times)
01:43:58   1> org.elasticsearch.transport.ConnectTransportException: [node_s0][127.0.0.1:40999] connect_exception
@astefan astefan added >test-failure Triaged test failures from CI :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. labels Feb 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Distributed)

@ywelsch ywelsch added the :Data Management/Stats Statistics tracking and retrieval APIs label Feb 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Stats)

@ywelsch ywelsch removed the :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. label Feb 17, 2020
@ywelsch
Copy link
Contributor

ywelsch commented Feb 17, 2020

I've investigated this and opened an issue here: #52411 as this is a more general problem than just this test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Stats Statistics tracking and retrieval APIs >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants