[jira] [Commented] (HIVE-20761) Select for update on notification_sequence table has retry interval and retries count too small.
[ https://issues.apache.org/jira/browse/HIVE-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16654620#comment-16654620 ] Hive QA commented on HIVE-20761: Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12944380/HIVE-20761.01.patch {color:red}ERROR:{color} -1 due to no test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 15096 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/14533/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14533/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14533/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.YetusPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase {noformat} This message is automatically generated. ATTACHMENT ID: 12944380 - PreCommit-HIVE-Build > Select for update on notification_sequence table has retry interval and > retries count too small. > > > Key: HIVE-20761 > URL: https://issues.apache.org/jira/browse/HIVE-20761 > Project: Hive > Issue Type: Bug > Components: HiveServer2, Metastore >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Minor > Labels: Metastore > Attachments: HIVE-20761.01.patch > > > Hive DDL's are intermittently failing with Error- Couldn't acquire the DB log > notification lock because we reached the maximum # of retries: 5 retries > {code:java} > Error while processing statement: FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Couldn't > acquire the DB log notification lock because we reached the maximum # of > retries: 5 retries. If this happens too often, then is recommended to > increase the maximum number of retries on the > hive.notification.sequence.lock.max.retries configuration :: Error executing > SQL query "select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for update".) > 2018-08-28 01:17:56,808|INFO|MainThread|machine.py:183 - > run()||GUID=94e6ff4d-5db8-45eb-8654-76f546e7f0b3|java.sql.SQLException: Error > while processing statement: FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Couldn't > acquire the DB log notification lock because we reached the maximum # of > retries: 5 retries. If this happens too often, then is recommended to > increase the maximum number of retries on the > hive.notification.sequence.lock.max.retries configuration :: Error executing > SQL query "select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for > update".){code} > It seems, metastore operations are slow in this cluster and hence concurrent > writes/DDL operations are failing to lock the row for update. > Currently, the sleep interval between retries is specified via the config > *hive.notification.sequence.lock.retry.sleep.interval*. The default value is > 500 ms which seems to be too small. Can we set higher values for sleep > interval and retries count, > *hive.notification.sequence.lock.retry.sleep.interval=10s* > *hive.notification.sequence.lock.max.retries=10* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-20761) Select for update on notification_sequence table has retry interval and retries count too small.
[ https://issues.apache.org/jira/browse/HIVE-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16654586#comment-16654586 ] Hive QA commented on HIVE-20761: | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 40s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m 23s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 43s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s{color} | {color:green} master passed {color} | | {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 28s{color} | {color:blue} common in master has 65 extant Findbugs warnings. {color} | | {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 2m 13s{color} | {color:blue} standalone-metastore/metastore-common in master has 28 extant Findbugs warnings. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 0s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 45s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 54s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 59s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 12s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 19m 22s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Optional Tests | asflicense javac javadoc findbugs checkstyle compile | | uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux | | Build tool | maven | | Personality | /data/hiveptest/working/yetus_PreCommit-HIVE-Build-14533/dev-support/hive-personality.sh | | git revision | master / 3c70302 | | Default Java | 1.8.0_111 | | findbugs | v3.0.0 | | modules | C: common standalone-metastore/metastore-common U: . | | Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-14533/yetus.txt | | Powered by | Apache Yetushttp://yetus.apache.org | This message was automatically generated. > Select for update on notification_sequence table has retry interval and > retries count too small. > > > Key: HIVE-20761 > URL: https://issues.apache.org/jira/browse/HIVE-20761 > Project: Hive > Issue Type: Bug > Components: HiveServer2, Metastore >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Minor > Labels: Metastore > Attachments: HIVE-20761.01.patch > > > Hive DDL's are intermittently failing with Error- Couldn't acquire the DB log > notification lock because we reached the maximum # of retries: 5 retries > {code:java} > Error while processing statement: FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Couldn't > acquire the DB log notification lock because we reached the maximum # of > retries: 5 retries. If this happens too often, then is recommended to > increase the maximum number of retries on the > hive.notification.sequence.lock.max.retries
[jira] [Commented] (HIVE-20761) Select for update on notification_sequence table has retry interval and retries count too small.
[ https://issues.apache.org/jira/browse/HIVE-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1665#comment-1665 ] Thejas M Nair commented on HIVE-20761: -- +1 pending tests > Select for update on notification_sequence table has retry interval and > retries count too small. > > > Key: HIVE-20761 > URL: https://issues.apache.org/jira/browse/HIVE-20761 > Project: Hive > Issue Type: Bug > Components: HiveServer2, Metastore >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Minor > Labels: Metastore > Attachments: HIVE-20761.01.patch > > > Hive DDL's are intermittently failing with Error- Couldn't acquire the DB log > notification lock because we reached the maximum # of retries: 5 retries > {code:java} > Error while processing statement: FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Couldn't > acquire the DB log notification lock because we reached the maximum # of > retries: 5 retries. If this happens too often, then is recommended to > increase the maximum number of retries on the > hive.notification.sequence.lock.max.retries configuration :: Error executing > SQL query "select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for update".) > 2018-08-28 01:17:56,808|INFO|MainThread|machine.py:183 - > run()||GUID=94e6ff4d-5db8-45eb-8654-76f546e7f0b3|java.sql.SQLException: Error > while processing statement: FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Couldn't > acquire the DB log notification lock because we reached the maximum # of > retries: 5 retries. If this happens too often, then is recommended to > increase the maximum number of retries on the > hive.notification.sequence.lock.max.retries configuration :: Error executing > SQL query "select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for > update".){code} > It seems, metastore operations are slow in this cluster and hence concurrent > writes/DDL operations are failing to lock the row for update. > Currently, the sleep interval between retries is specified via the config > *hive.notification.sequence.lock.retry.sleep.interval*. The default value is > 500 ms which seems to be too small. Can we set higher values for sleep > interval and retries count, > *hive.notification.sequence.lock.retry.sleep.interval=10s* > *hive.notification.sequence.lock.max.retries=10* -- This message was sent by Atlassian JIRA (v7.6.3#76005)