Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

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

avatar
New Contributor

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? 

1 ACCEPTED SOLUTION

avatar
New Contributor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
2 REPLIES 2

avatar

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?

avatar
New Contributor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login