Fix ref count handling in Engine.failEngine (#48639) #48646

original-brownbear · 2019-10-29T17:24:53Z

We can run into an already closed store here and hence
throw on trying to increment the ref count => moving to
the guarded ref count increment

closes #48625

backport of #48639

We can run into an already closed store here and hence throw on trying to increment the ref count => moving to the guarded ref count increment closes elastic#48625

elasticmachine · 2019-10-29T17:24:55Z

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

We can run into an already closed store here and hence throw on trying to increment the ref count => moving to the guarded ref count increment closes #48625

Fix ref count handling in Engine.failEngine (elastic#48639)

ce1c9c0

We can run into an already closed store here and hence throw on trying to increment the ref count => moving to the guarded ref count increment closes elastic#48625

original-brownbear added :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. backport labels Oct 29, 2019

original-brownbear merged commit 01e326d into elastic:7.x Oct 30, 2019

original-brownbear deleted the 48639-7.x branch October 30, 2019 09:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix ref count handling in Engine.failEngine (#48639) #48646

Fix ref count handling in Engine.failEngine (#48639) #48646

original-brownbear commented Oct 29, 2019

elasticmachine commented Oct 29, 2019

Fix ref count handling in Engine.failEngine (#48639) #48646

Fix ref count handling in Engine.failEngine (#48639) #48646

Conversation

original-brownbear commented Oct 29, 2019

elasticmachine commented Oct 29, 2019