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

"Failed to clear scroll" when reindexing from 1.x to 5.2.0 #22937

Closed
PhaedrusTheGreek opened this issue Feb 2, 2017 · 1 comment

Comments

Projects
None yet
3 participants
@PhaedrusTheGreek
Copy link
Contributor

commented Feb 2, 2017

Environment:
Reindexing from ES 1.7.5 -> ES 5.2.0

Description:

This error message is output repeatedly during reindex. The reindex can complete successfully, but perhaps not efficiently.

2017-02-02T13:02:16,867][WARN ][o.e.i.r.TransportReindexAction] [CBuuMNt] Failed to clear scroll [c2NhbjswOzE7dG90YWxfaGl0czoyOw==]
org.elasticsearch.client.ResponseException: DELETE http://127.0.0.1:9201/_search/scroll: HTTP/1.1 404 Not Found
{}
	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:311) [rest-5.2.0.jar:5.2.0]
	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:300) [rest-5.2.0.jar:5.2.0]
	at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119) [httpcore-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177) [httpasyncclient-4.1.2.jar:4.1.2]
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:436) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:326) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) [httpasyncclient-4.1.2.jar:4.1.2]
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) [httpasyncclient-4.1.2.jar:4.1.2]
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) [httpcore-nio-4.4.5.jar:4.4.5]
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588) [httpcore-nio-4.4.5.jar:4.4.5]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]

Notable:

  • Problem does not happen with 1.x -> 5.1.x
  • Problem does not happen with 2.x -> 5.2.0

@nik9000 nik9000 self-assigned this Feb 2, 2017

@nik9000

This comment has been minimized.

Copy link
Contributor

commented Feb 2, 2017

I saw it today. This comes from a fix we did in 5.2 where we were more careful to actually clear the scroll, I think. I'll investigate, but I believe it can safely be ignored.

@nik9000 nik9000 added the >bug label Feb 2, 2017

nik9000 added a commit to nik9000/elasticsearch that referenced this issue Feb 2, 2017

Reindex: do not log when can't clear old scroll
Versions of Elasticsearch prior to 2.0 would return a scroll id
even with the last scroll response. They'd then automatically
clear the scroll because it is empty. When terminating reindex
will attempt to clear the last scroll it received, regardless of
the remote version. This quiets the warning when the scroll cannot
be cleared for versions before 2.0.

Closes elastic#22937

nik9000 added a commit that referenced this issue Feb 3, 2017

Reindex: do not log when can't clear old scroll (#22942)
Versions of Elasticsearch prior to 2.0 would return a scroll id
even with the last scroll response. They'd then automatically
clear the scroll because it is empty. When terminating reindex
will attempt to clear the last scroll it received, regardless of
the remote version. This quiets the warning when the scroll cannot
be cleared for versions before 2.0.

Closes #22937

nik9000 added a commit that referenced this issue Feb 3, 2017

Reindex: do not log when can't clear old scroll (#22942)
Versions of Elasticsearch prior to 2.0 would return a scroll id
even with the last scroll response. They'd then automatically
clear the scroll because it is empty. When terminating reindex
will attempt to clear the last scroll it received, regardless of
the remote version. This quiets the warning when the scroll cannot
be cleared for versions before 2.0.

Closes #22937

nik9000 added a commit that referenced this issue Feb 3, 2017

Reindex: do not log when can't clear old scroll (#22942)
Versions of Elasticsearch prior to 2.0 would return a scroll id
even with the last scroll response. They'd then automatically
clear the scroll because it is empty. When terminating reindex
will attempt to clear the last scroll it received, regardless of
the remote version. This quiets the warning when the scroll cannot
be cleared for versions before 2.0.

Closes #22937
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.