hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <>
Subject [jira] [Created] (HIVE-17758) NOTIFICATION_SEQUENCE_LOCK_RETRY_SLEEP_INTERVAL.defaultLongVal is -1
Date Tue, 10 Oct 2017 12:34:00 GMT
Zoltan Haindrich created HIVE-17758:

             Summary: NOTIFICATION_SEQUENCE_LOCK_RETRY_SLEEP_INTERVAL.defaultLongVal is -1
                 Key: HIVE-17758
             Project: Hive
          Issue Type: Bug
            Reporter: Zoltan Haindrich

HIVE-16886 introduced a retry logic; which has a configurable retry interval. unfortunately
{{HiveConf}} has some public fields which at first glance seems to be usefull to pass as arguments
to other methods - but in this case the default value is not even loaded into the field read
by the code.. and because of that the innocent client code [here|]
 have used a {{-1}} value incorrectly which eventually caused an exception [here|]:
2017-10-10 11:22:37,638 ERROR [load-dynamic-partitions-12]: metastore.ObjectStore (
- could not get lock for update
java.lang.IllegalArgumentException: timeout value is negative
        at java.lang.Thread.sleep(Native Method)
        at org.apache.hadoop.hive.metastore.ObjectStore$
        at org.apache.hadoop.hive.metastore.ObjectStore.lockForUpdate(
        at org.apache.hadoop.hive.metastore.ObjectStore.addNotificationEvent(
        at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(

This message was sent by Atlassian JIRA

View raw message