Details
Minor Description
The DbNotificationListener class has a separate thread which cleans the old notifications from the database. Here is the snippet from the run method.
public void run() {
while (true) {
rs.cleanNotificationEvents(ttl);
LOG.debug("Cleaner thread done");
try {
Thread.sleep(sleepTime);
} catch (InterruptedException e) {
LOG.info("Cleaner thread sleep interrupted", e);
}
}
}
If rs.cleanNotificationEvents throws a RuntimeException which datanucleus can throw the exception remains uncaught and the thread will die. This can lead to older notifications never getting cleaned until we restart HMS. Given that many operations generate loads of events, the notification log table can quickly have thousands of rows which are never get cleaned up.
Attachments
Attachments
Issue Links
- is related to
-
HIVE-18885 DbNotificationListener has a deadlock between Java and DB locks (2.x line)
-
- Closed
-
- links to
