Skip to main content
Hadoop_dev
Hadoop_dev
Gold ⭐️
March 22, 2021
Solved

Will updating hive.notification.sequence.lock.max.retries cause SocketTimeOut exception?

Hi, 

 

We  recently updated  value of hive.notification.sequence.lock.max.retries from 20 to 40 and started getting multiple SocketTimeOut Failures 

Caused by: java.io.IOException: java.net.SocketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/10.2.1.11:49971 remote=node011.mapreduce.net/10.2.8.4:45454]
at org.apache.hadoop.ipc.Client$Connection$1.run(Client.java:685).  .  

.Is this related? 

Hadoop_dev
Hadoop_devAnswer
Gold ⭐️
March 30, 2021

Hi,

 

I Saw this error while  select data  from one hive table and insert it to other.  It is resolved now  after restarting yarn.

View in thread

2 replies

mugdha
Gold ⭐️⭐️
mugdha
Gold ⭐️⭐️
March 23, 2021

The 'hive.notification.sequence.lock.max.retries' Parameter detects the number of retries for acquiring a Lock for getting the Next Notification ID for entries in the 'NOTIFICATION_LOG' Table.

 

The error that you are seeing does seem to be because of this. Add more context, when are you seeing this? What job are you running? Full trace?

Translate
Hadoop_dev
Hadoop_devAuthorAnswer
Gold ⭐️
March 30, 2021

Hi,

 

I Saw this error while  select data  from one hive table and insert it to other.  It is resolved now  after restarting yarn.

Translate
Terms & ConditionsAccessibility statement