-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
CcrRollingUpgradeIT fails on CI #59625
Comments
Pinging @elastic/es-distributed (:Distributed/CCR) |
Another failure: https://gradle-enterprise.elastic.co/s/mkzyvj65xtfkc |
And another: https://gradle-enterprise.elastic.co/s/jfzdfqa6fi4jc @dnhatn should this be muted while you're taking a look at it? |
Updated `_nodes/stats`: * Update `script` in `_node/stats` to include stats per context: ``` "script": { "compilations": 1, "cache_evictions": 0, "compilation_limit_triggered": 0, "contexts":[ { "context": "aggregation_selector", "compilations": 0, "cache_evictions": 0, "compilation_limit_triggered": 0 }, ``` Refs: elastic#50152 Backport: elastic#59625
Thanks @dakrone. I've muted this suite. |
I backported the mute commit to 7.9 as it was failing there regularly also |
If a primary shard of a follower index is being relocated, then we will fail to create a follow-task. This validation is too restricted. We should ensure that all primaries of the follower index are active instead. Closes #59625
If a primary shard of a follower index is being relocated, then we will fail to create a follow-task. This validation is too restricted. We should ensure that all primaries of the follower index are active instead. Closes #59625
If a primary shard of a follower index is being relocated, then we will fail to create a follow-task. This validation is too restricted. We should ensure that all primaries of the follower index are active instead. Closes #59625
If a primary shard of a follower index is being relocated, then we will fail to create a follow-task. This validation is too restricted. We should ensure that all primaries of the follower index are active instead. Closes #59625
If a primary shard of a follower index is being relocated, then we will fail to create a follow-task. This validation is too restricted. We should ensure that all primaries of the follower index are active instead. Closes #59625
@arteam and I spotted that this test suite is still muted in 7.x: https://github.com/elastic/elasticsearch/blob/7.x/x-pack/qa/rolling-upgrade-multi-cluster/src/test/java/org/elasticsearch/upgrades/CcrRollingUpgradeIT.java#L32 Is there a reason for this? |
@martijnvg I've opened #76765. |
This test started to fail regularly since July 14th 2020. The logs show some errors related to component templates but this should be addressed by #59624.
Build scan:
https://gradle-enterprise.elastic.co/s/uxnrmjs7mcwve
https://gradle-enterprise.elastic.co/s/li64mi23adjtm
https://gradle-enterprise.elastic.co/s/uza2ofj3d32fe
Applicable branches: 7.x
Failure history:
https://build-stats.elastic.co/app/kibana#/discover?_g=(refreshInterval:(pause:!t,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:e58bf320-7efd-11e8-bf69-63c8ef516157,interval:auto,query:(language:lucene,query:'class:%22org.elasticsearch.upgrades.CcrRollingUpgradeIT%22'),sort:!(time,desc))
The text was updated successfully, but these errors were encountered: