[
https://issues.apache.org/jira/browse/HIVE-24077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205455#comment-17205455
]
Peter Varga edited comment on HIVE-24077 at 10/1/20, 12:23 PM:
---------------------------------------------------------------
[~scarlin] could you please take a look at the TestStreaming tests, they became
flaky. It seems like the Heartbeater threads are causing problems, I do not
know if it is the tests fault or not.
https://issues.apache.org/jira/browse/HIVE-24219
was (Author: pvargacl):
[~scarlin] could you please take a look at the TestStreaming tests, they became
flaky. It seems like the Heartbeater threads are causing problems, I do not
know if it is the tests falt or not.
https://issues.apache.org/jira/browse/HIVE-24219
> Streaming Ingest v2 does not send heartbeats
> --------------------------------------------
>
> Key: HIVE-24077
> URL: https://issues.apache.org/jira/browse/HIVE-24077
> Project: Hive
> Issue Type: Bug
> Components: Streaming
> Reporter: Matt Burgess
> Assignee: Steve Carlin
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Hive Streaming v2, TransactionBatch calls setupHeartbeatThread() before
> setting minTxnId to an AtomicLong object, so the value that is used for
> HeartbeatRunnable is null. Upon the first call to run(), a
> NullPointerException is thrown by the minTxnId.get() call, which causes the
> thread to fail and it does not get rescheduled. This causes any transaction
> that exceeds the transaction timeout time (default 5 mins) to be aborted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
