You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/05/07 13:36:03 UTC

[GitHub] [incubator-druid] mihai-cazacu-adswizz edited a comment on issue #7597: [materialized view] The generated specification is too big

mihai-cazacu-adswizz edited a comment on issue #7597: [materialized view] The generated specification is too big
URL: https://github.com/apache/incubator-druid/issues/7597#issuecomment-490081669
 
 
   I have increased the `druid.indexer.runner.maxZnodeBytes` value to `2.5MB` and everything worked fine until the Supervisor reached an interval with many segments (the [created JSON](https://github.com/apache/incubator-druid/blob/master/indexing-service/src/main/java/org/apache/druid/indexing/overlord/RemoteTaskRunner.java#L863) has ~ `1.5MB`). Starting from this point,  the `Waiting Tasks - Tasks waiting on locks` section in Overlord was filled with dozens of MV tasks (for the same data source: `index_materialized_view_test_2019-05-07...`). 
   
   The error:
   
   ```
   ERROR [LeaderSelector[/druid/druid-prod/overlord/_OVERLORD]] org.apache.druid.curator.discovery.CuratorDruidLeaderSelector - listener becomeLeader() failed. Unable to become leader: {class=org.apache.druid.curator.discovery.CuratorDruidLeaderSelector, exceptionType=class org.apache.druid.java.util.common.ISE, exceptionMessage=Could not reacquire lock on interval[2019-02-21T00:00:00.000Z/2019-02-22T00:00:00.000Z] version[2019-05-07T11:24:03.543Z] for task: index_materialized_view_test_2019-05-07T11:16:05.026Z}
   org.apache.druid.java.util.common.ISE: Could not reacquire lock on interval[2019-02-21T00:00:00.000Z/2019-02-22T00:00:00.000Z] version[2019-05-07T11:24:03.543Z] for task: index_materialized_view_test_2019-05-07T11:16:05.026Z
           at org.apache.druid.indexing.overlord.TaskLockbox.syncFromStorage(TaskLockbox.java:171) ~[druid-indexing-service-0.13.0-incubating.jar:0.13.0-incubating]
           at org.apache.druid.indexing.overlord.TaskMaster$1.becomeLeader(TaskMaster.java:109) ~[druid-indexing-service-0.13.0-incubating.jar:0.13.0-incubating]
           at org.apache.druid.curator.discovery.CuratorDruidLeaderSelector$1.isLeader(CuratorDruidLeaderSelector.java:98) [druid-server-0.13.0-incubating.jar:0.13.0-incubating]
           at org.apache.curator.framework.recipes.leader.LeaderLatch$9.apply(LeaderLatch.java:665) [curator-recipes-4.0.0.jar:4.0.0]
           at org.apache.curator.framework.recipes.leader.LeaderLatch$9.apply(LeaderLatch.java:661) [curator-recipes-4.0.0.jar:4.0.0]
           at org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:93) [curator-framework-4.0.0.jar:4.0.0]
           at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_201]
           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_201]
           at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
   ```
   
   Because of this error, the Overlord has stopped to respond.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org