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 2021/08/19 21:25:49 UTC
[GitHub] [druid] vrrs edited a comment on issue #11592: Overlord spins 300% and consumes all -Xmx even though Middle Managers are idle.
vrrs edited a comment on issue #11592:
URL: https://github.com/apache/druid/issues/11592#issuecomment-902258315
I have the same issue. I increased the heap from 3gb to 16gb. I can see this on the logs
```
2021-08-19T00:16:29,763 WARN [qtp2009492047-84] org.apache.druid.java.util.common.RetryUtils - Retrying (4 of 9) in 10,348ms.
org.skife.jdbi.v2.exceptions.CallbackFailedException: org.skife.jdbi.v2.exceptions.UnableToExecuteStatementException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
The last packet successfully received from the server was 0 milliseconds ago. The last packet sent successfully to the server was 13,316 milliseconds ago. [statement:"SELECT id, status_payload, created_date, datasource, payload FROM druid_tasks WHERE active = FALSE AND created_date >= :start ORDER BY created_date DESC", located:"SELECT id, status_payload, created_date, datasource, payload FROM druid_tasks WHERE active = FALSE AND created_date >= :start ORDER BY created_date DESC", rewritten:"SELECT id, status_payload, created_date, datasource, payload FROM druid_tasks WHERE active = FALSE AND created_date >= ? ORDER BY created_date DESC", arguments:{ positional:{}, named:{start:'2021-08-18T00:14:42.483Z'}, finder:[]}]
at org.skife.jdbi.v2.DBI.withHandle(DBI.java:284) ~[jdbi-2.63.1.jar:2.63.1]
at org.apache.druid.metadata.SQLMetadataConnector.lambda$retryWithHandle$0(SQLMetadataConnector.java:145) ~[druid-server-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.java.util.common.RetryUtils.retry(RetryUtils.java:87) ~[druid-core-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.java.util.common.RetryUtils.retry(RetryUtils.java:115) ~[druid-core-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.java.util.common.RetryUtils.retry(RetryUtils.java:105) ~[druid-core-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.metadata.SQLMetadataConnector.retryWithHandle(SQLMetadataConnector.java:145) ~[druid-server-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.metadata.SQLMetadataConnector.retryWithHandle(SQLMetadataConnector.java:155) ~[druid-server-0.20.0-iap3.3.jar:0.20.0-iap3.3]
at org.apache.druid.metadata.SQLMetadataStorageActionHandler.getCompletedTaskInfo(SQLMetadataStorageActionHandler.java:277) ~[druid-server-0.20.0-iap3.3.jar:0.20.0-iap3.3]
```
I thought it was a db failure but i can make the same query from a docker mysql client to the same host and it works fine.
Im using
```
druid.indexer.runner.type=remote
druid.indexer.storage.type=metadata
```
--
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.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org