You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2020/02/25 12:38:00 UTC
[jira] [Commented] (UNOMI-271) Creating around 20 segments at once
will break unomi
[ https://issues.apache.org/jira/browse/UNOMI-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044402#comment-17044402 ]
Serge Huber commented on UNOMI-271:
-----------------------------------
Thanks Yakub,
I'm copying the exception here:
{code}
[2020-02-14T11:33:02,915][DEBUG][o.e.a.s.TransportSearchAction] [yakub-XPS13] [context-segment][1], node[KFzEVT9YRj2LWzuiH29WrA], [P], s[STARTED], a[id=h4Z32W1NTCWzkAxGnwd2qA]: Failed to execute [SearchRequest{searchType=QUERY_THEN_FETCH, indices=[context-segment], indicesOptions=IndicesOptions[ignore_unavailable=false, allow_no_indices=true, expand_wildcards_open=true, expand_wildcards_closed=false, allow_aliases_to_multiple_indices=true, forbid_closed_indices=true, ignore_aliases=false, ignore_throttled=true], types=[], routing='null', preference='null', requestCache=null, scroll=Scroll{keepAlive=1h}, maxConcurrentShardRequests=0, batchedReduceSize=512, preFilterShardSize=128, allowPartialSearchResults=true, localClusterAlias=null, getOrCreateAbsoluteStartMillis=-1, ccsMinimizeRoundtrips=true, source={"from":0,"size":10,"query":{"match_all":{"boost":1.0}},"version":true,"_source":{"includes":[],"excludes":[]}}}]
org.elasticsearch.transport.RemoteTransportException: [yakub-XPS13][127.0.0.1:9300][indices:data/read/search[phase/query]]
Caused by: org.elasticsearch.ElasticsearchException: Trying to create too many scroll contexts. Must be less than or equal to: [500]. This limit can be set by changing the [search.max_open_scroll_context] setting.
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:542) ~[elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:348) ~[elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.search.SearchService.lambda$executeQueryPhase$1(SearchService.java:340) ~[elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.action.ActionListener.lambda$map$2(ActionListener.java:145) ~[elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:62) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.search.SearchService.lambda$rewriteShardRequest$7(SearchService.java:1043) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.action.ActionRunnable$1.doRun(ActionRunnable.java:45) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:44) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773) [elasticsearch-7.4.2.jar:7.4.2]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-7.4.2.jar:7.4.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:830) [?:?]
{code}
It seems to me like there might be a scroll leak.
> Creating around 20 segments at once will break unomi
> ----------------------------------------------------
>
> Key: UNOMI-271
> URL: https://issues.apache.org/jira/browse/UNOMI-271
> Project: Apache Unomi
> Issue Type: Bug
> Components: build, core
> Affects Versions: 1.5.0
> Reporter: Yakub Ilyasov
> Priority: Major
>
> Made a script to test ComparisonOperators, but I found out creating a lot of segment in a short time will cause unomi to break for a little while.
> Code: [https://github.com/IlyasovYakub/test_comparison_operator]
> More info can be found in the wiki of the code.
> I thought I might let you guys know this happens :)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)