Skip to content

Conversation

@dnhatn
Copy link
Member

@dnhatn dnhatn commented Oct 24, 2019

We should not suppress the exception and fail translog if we fail to close the reader.

@dnhatn dnhatn added >bug :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. v8.0.0 v7.6.0 labels Oct 24, 2019
@elasticmachine
Copy link
Collaborator

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

Copy link
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an underlying problem with how this is handled today?

Closing the reader only closes the underlying file channel. Given that the reader is dead/unused info anyway, it seems excessive to fail the translog due to failing to close the channel? Just like we ignore exceptions if we cannot delete the files afterwards.

@dnhatn
Copy link
Member Author

dnhatn commented Oct 28, 2019

@henningandersen Yes, I agree. It's too harsh to fail translog in this case. Thank you for looking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. v7.6.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants