Data disappeared in Kapua UI [message #1840868] |
Tue, 27 April 2021 10:16  |
Etienne Villedieu Messages: 2 Registered: April 2021 |
Junior Member |
|
|
Hello,
From this morning all the data has disappeared of the "By Topic" section in the UI.
The data can be retrieved in the "By Device" section or with the APIs.
This error 500 message is displayed when accessing "By Topic" :
Quote:
Request Query returned with 500 HTTP response code. Error: Internal Server Error
Here are ElasticSearch's logs :
Quote:
[2021-04-26T00:50:00,001][INFO ][o.e.x.m.MlDailyMaintenanceService] [WneNZ-F] triggering scheduled [ML] maintenance tasks
[2021-04-26T00:50:00,001][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [WneNZ-F] Deleting expired data
[2021-04-26T00:50:00,006][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [WneNZ-F] Completed deletion of expired ML data
[2021-04-26T00:50:00,006][INFO ][o.e.x.m.MlDailyMaintenanceService] [WneNZ-F] Successfully completed [ML] maintenance tasks
[2021-04-26T10:08:55,774][INFO ][o.e.c.m.MetaDataMappingService] [WneNZ-F] [2949571327289794593-2021-18/1p4u_6LVSHiTW1dr18g9EQ] update_mapping [_doc]
[2021-04-27T00:50:00,001][INFO ][o.e.x.m.MlDailyMaintenanceService] [WneNZ-F] triggering scheduled [ML] maintenance tasks
[2021-04-27T00:50:00,001][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [WneNZ-F] Deleting expired data
[2021-04-27T00:50:00,004][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [WneNZ-F] Completed deletion of expired ML data
[2021-04-27T00:50:00,004][INFO ][o.e.x.m.MlDailyMaintenanceService] [WneNZ-F] Successfully completed [ML] maintenance tasks
[2021-04-27T09:22:13,694][WARN ][r.suppressed ] [WneNZ-F] path: /.2949571327289794593-channel/_search, params: {index=.2949571327289794593-channel}
org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed
at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseFailure(AbstractSearchAsyncAction.java:296) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.AbstractSearchAsyncAction.executeNextPhase(AbstractSearchAsyncAction.java:133) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseDone(AbstractSearchAsyncAction.java:259) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase.onShardFailure(InitialSearchPhase.java:100) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase.access$100(InitialSearchPhase.java:48) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase$2.lambda$onFailure$1(InitialSearchPhase.java:220) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase.maybeFork(InitialSearchPhase.java:174) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase.access$000(InitialSearchPhase.java:48) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.InitialSearchPhase$2.onFailure(InitialSearchPhase.java:220) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.SearchExecutionStatsCollector.onFailure(SearchExecutionStatsCollector.java:73) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:59) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.search.SearchTransportService$ConnectionCountingHandler.handleException(SearchTransportService.java:463) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1114) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:1226) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:1200) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.transport.TaskTransportChannel.sendResponse(TaskTransportChannel.java:60) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.action.support.ChannelActionListener.onFailure(ChannelActionListener.java:56) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.SearchService$2.onFailure(SearchService.java:367) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:361) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:355) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.SearchService$4.doRun(SearchService.java:1107) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:41) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:751) [elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.8.7.jar:6.8.7]
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) [?:?]
Caused by: org.elasticsearch.search.query.QueryPhaseExecutionException: Result window is too large, from + size must be less than or equal to: [10000] but was [10250]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting.
at org.elasticsearch.search.DefaultSearchContext.preProcess(DefaultSearchContext.java:212) ~[elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.query.QueryPhase.preProcess(QueryPhase.java:91) ~[elasticsearch-6.8.7.jar:6.8.7]
at org.elasticsearch.search.SearchService.createContext(SearchService.java:649) ~[elasticsearch-6.8.7.jar:6.8.7]
Thank you for your help,
Etienne
|
|
|
|
Powered by
FUDForum. Page generated in 0.02386 seconds