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
Failed node exception due to translog already closed #23099
Comments
@pickypg I'm assigning this to you as it seems you plan to pick this up. We can debate whether node stats should return errors to the users (rather than log them under WARN) but this is not the cause of this issue. I believe this goes wrong now because we stopped wrapping up internal engine exceptions and that confuses the logic here. I think we should teach that clause about AlreadyClosedException. The shard was just closed concurrently to the stats call, which is not a problem |
@bleskes I totally agree that this is a fake failure, but I do wonder about the value of ever throwing away exceptions to a In addition to making the appropriate fix here, I wonder if a secondary fix would be to remove the |
I tend to agree - we should report what happened to the use. It will put an extra burden on finding the right exceptions to ignore, but I think it's the right tradeoff. IMO it should be a separate change. |
Agree it should be a separate change. |
Going to fix this by:
|
This is also occurring with |
This was merged and backported to the respective branches both PRs. Thanks! |
Elasticsearch version: 5.2.0
Plugins installed: found-elasticsearch repository-s3 x-pack (default cloud set)
JVM version: java version "1.8.0_72"
Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
OS version: Ubuntu 14.04.1 LTS
Description of the problem including expected versus actual behavior:
Unclear on resulting behavior, but got a ran into it with the following logs.
Provide logs (if relevant):
[2017-02-10T05:10:35,904][WARN ][org.elasticsearch.action.admin.cluster.node.stats.TransportNodesStatsAction] not accumulating exceptions, excluding exception from response org.elasticsearch.action.FailedNodeException: Failed node [WmfKMkelS7qOP_43OOpkVA]
The text was updated successfully, but these errors were encountered: