[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[ https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519870#comment-14519870 ] Alan Gates commented on HIVE-10500: --- Yes, I transposed two numbers in the commit message. I looked at how to fix it but according to the documentation I read doing a 'git amend' would actually change the hash of the commit, which looked likely to do more damage than it fixed. > Repeated deadlocks in underlying RDBMS cause transaction or lock failure > > > Key: HIVE-10500 > URL: https://issues.apache.org/jira/browse/HIVE-10500 > Project: Hive > Issue Type: Bug > Components: Transactions >Affects Versions: 0.14.0, 1.0.0, 1.1.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 1.2.0 > > Attachments: HIVE-10050.patch > > > In some cases in a busy system, deadlocks in the metastore RDBMS can cause > failures in Hive locks and transactions when using DbTxnManager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[ https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518978#comment-14518978 ] Lefty Leverenz commented on HIVE-10500: --- If the trunk commit is 8981f365bf0cf921bc0ac2ff8914df44ca2f7de7 then it has a typo in the JIRA number: "HIVE-10050 Added backoff for deadlock retry. Also make sure to reset the deadlock counter at appropriate points." > Repeated deadlocks in underlying RDBMS cause transaction or lock failure > > > Key: HIVE-10500 > URL: https://issues.apache.org/jira/browse/HIVE-10500 > Project: Hive > Issue Type: Bug > Components: Transactions >Affects Versions: 0.14.0, 1.0.0, 1.1.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 1.2.0 > > Attachments: HIVE-10050.patch > > > In some cases in a busy system, deadlocks in the metastore RDBMS can cause > failures in Hive locks and transactions when using DbTxnManager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[ https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518233#comment-14518233 ] Alan Gates commented on HIVE-10500: --- [~ekoifman], I didn't change the log level as that was already that way. This patch doesn't make it worse. If we find it to be a problem we can change it separately. > Repeated deadlocks in underlying RDBMS cause transaction or lock failure > > > Key: HIVE-10500 > URL: https://issues.apache.org/jira/browse/HIVE-10500 > Project: Hive > Issue Type: Bug > Components: Transactions >Affects Versions: 0.14.0, 1.0.0, 1.1.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 1.2.0 > > Attachments: HIVE-10050.patch > > > In some cases in a busy system, deadlocks in the metastore RDBMS can cause > failures in Hive locks and transactions when using DbTxnManager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[
https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517654#comment-14517654
]
Eugene Koifman commented on HIVE-10500:
---
would "LOG.warn("Deadlock detected in " + caller + ", trying again.");" flood
the log on a busy system?
perhaps this should be info or every Nth occurence
> Repeated deadlocks in underlying RDBMS cause transaction or lock failure
>
>
> Key: HIVE-10500
> URL: https://issues.apache.org/jira/browse/HIVE-10500
> Project: Hive
> Issue Type: Bug
> Components: Transactions
>Affects Versions: 0.14.0, 1.0.0, 1.1.0
>Reporter: Alan Gates
>Assignee: Alan Gates
> Attachments: HIVE-10050.patch
>
>
> In some cases in a busy system, deadlocks in the metastore RDBMS can cause
> failures in Hive locks and transactions when using DbTxnManager
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[ https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517560#comment-14517560 ] Gunther Hagleitner commented on HIVE-10500: --- +1 > Repeated deadlocks in underlying RDBMS cause transaction or lock failure > > > Key: HIVE-10500 > URL: https://issues.apache.org/jira/browse/HIVE-10500 > Project: Hive > Issue Type: Bug > Components: Transactions >Affects Versions: 0.14.0, 1.0.0, 1.1.0 >Reporter: Alan Gates >Assignee: Alan Gates > Attachments: HIVE-10050.patch > > > In some cases in a busy system, deadlocks in the metastore RDBMS can cause > failures in Hive locks and transactions when using DbTxnManager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[
https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516321#comment-14516321
]
Hive QA commented on HIVE-10500:
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12728482/HIVE-10050.patch
{color:red}ERROR:{color} -1 due to 16 failed/errored test(s), 8818 tests
executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-bucketmapjoin6.q-constprog_partitioner.q-infer_bucket_sort_dyn_part.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-external_table_with_space_in_location_path.q-infer_bucket_sort_merge.q-auto_sortmerge_join_16.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-groupby2.q-import_exported_table.q-bucketizedhiveinputformat.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-index_bitmap3.q-stats_counter_partitioned.q-temp_table_external.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_map_operators.q-join1.q-bucketmapjoin7.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_num_buckets.q-disable_merge_for_bucketing.q-uber_reduce.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-infer_bucket_sort_reducers_power_two.q-scriptfile1.q-scriptfile1_win.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-leftsemijoin_mr.q-load_hdfs_file_with_space_in_the_name.q-root_dir_external_table.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-list_bucket_dml_10.q-bucket_num_reducers.q-bucket6.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-load_fs2.q-file_with_header_footer.q-ql_rewrite_gbtoidx_cbo_1.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-parallel_orderby.q-reduce_deduplicate.q-ql_rewrite_gbtoidx_cbo_2.q-and-1-more
- did not produce a TEST-*.xml file
TestMinimrCliDriver-ql_rewrite_gbtoidx.q-smb_mapjoin_8.q - did not produce a
TEST-*.xml file
TestMinimrCliDriver-schemeAuthority2.q-bucket4.q-input16_cc.q-and-1-more - did
not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udaf_histogram_numeric
org.apache.hive.jdbc.TestSSL.testSSLConnectionWithProperty
org.apache.hive.spark.client.TestSparkClient.testRemoteClient
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3617/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3617/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3617/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 16 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12728482 - PreCommit-HIVE-TRUNK-Build
> Repeated deadlocks in underlying RDBMS cause transaction or lock failure
>
>
> Key: HIVE-10500
> URL: https://issues.apache.org/jira/browse/HIVE-10500
> Project: Hive
> Issue Type: Bug
> Components: Transactions
>Affects Versions: 0.14.0, 1.0.0, 1.1.0
>Reporter: Alan Gates
>Assignee: Alan Gates
> Attachments: HIVE-10050.patch
>
>
> In some cases in a busy system, deadlocks in the metastore RDBMS can cause
> failures in Hive locks and transactions when using DbTxnManager
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-10500) Repeated deadlocks in underlying RDBMS cause transaction or lock failure
[ https://issues.apache.org/jira/browse/HIVE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514893#comment-14514893 ] Sushanth Sowmyan commented on HIVE-10500: - Approved for 1.2, added to https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status You can go ahead and commit this to 1.2 when you commit it to trunk. > Repeated deadlocks in underlying RDBMS cause transaction or lock failure > > > Key: HIVE-10500 > URL: https://issues.apache.org/jira/browse/HIVE-10500 > Project: Hive > Issue Type: Bug > Components: Transactions >Affects Versions: 0.14.0, 1.0.0, 1.1.0 >Reporter: Alan Gates >Assignee: Alan Gates > Attachments: HIVE-10050.patch > > > In some cases in a busy system, deadlocks in the metastore RDBMS can cause > failures in Hive locks and transactions when using DbTxnManager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
