[
https://issues.apache.org/jira/browse/HIVE-26947?focusedWorklogId=841107&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-841107
]
ASF GitHub Bot logged work on HIVE-26947:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/23 13:03
Start Date: 23/Jan/23 13:03
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on code in PR #3955:
URL: https://github.com/apache/hive/pull/3955#discussion_r1084029943
##########
common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:
##########
@@ -3215,6 +3215,10 @@ public static enum ConfVars {
"Time in seconds after which a compaction job will be declared failed
and the\n" +
"compaction re-queued."),
+ HIVE_COMPACTOR_WORKER_SLEEP_TIME("hive.compactor.worker.sleep.time",
"10000ms",
Review Comment:
do we really need to expose this complexity to the end users? they already
have plenty of parameters to tweak.
Issue Time Tracking
-------------------
Worklog Id: (was: 841107)
Time Spent: 4h 20m (was: 4h 10m)
> Hive compactor.Worker can respawn connections to HMS at extremely high
> frequency
> --------------------------------------------------------------------------------
>
> Key: HIVE-26947
> URL: https://issues.apache.org/jira/browse/HIVE-26947
> Project: Hive
> Issue Type: Bug
> Reporter: Akshat Mathur
> Assignee: Akshat Mathur
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> After catching the exception generated by the findNextCompactionAndExecute()
> task, HS2 appears to immediately rerun the task with no delay or backoff. As
> a result there are ~3500 connection attempts from HS2 to HMS over just a 5
> second period in the HS2 log
> The compactor.Worker should wait between failed attempts and maybe do an
> exponential backoff.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
