ot;user@hive.apache.org"
> Subject: Re: Transaction deadlocks
>
> that’s indeed a problem.
>
> From: Steve Howard
> Reply-To: "user@hive.apache.org"
> Date: Tuesday, September 22, 2015 at 6:48 PM
> To: "user@hive.apache.org"
> Subject: Re: Transac
e.org<mailto:user@hive.apache.org>"
mailto:user@hive.apache.org>>
Subject: Re: Transaction deadlocks
that’s indeed a problem.
From: Steve Howard mailto:stevedhow...@gmail.com>>
Reply-To: "user@hive.apache.org<mailto:user@hive.apache.org>"
mailto:user@hive.apache.org&
:user@hive.apache.org>"
mailto:user@hive.apache.org>>
Subject: Re: Transaction deadlocks
Am I missing it, or do you reset the deadlock count to 0 every time the lock
method is taken, so the ten count is never reached in checkRetryable()?
public LockResponse lock(LockRequest rqst)
eached. Last error: " + getMessage(e));
> this.retryNum = 0;
> }
> else
> {
> this.deadlockCnt = 0;
> this.retryNum = 0;
> }
> }
>
> Thanks,
>
> Steve
>
> On Tue, Sep 22, 2015 at 6:22 PM, Eugene Koifman
> wrote
ryNum = 0;
}
else
{
this.deadlockCnt = 0;
this.retryNum = 0;
}
}
Thanks,
Steve
On Tue, Sep 22, 2015 at 6:22 PM, Eugene Koifman
wrote:
> What version of Hive are you running? In the current codebase at least,
> TxnHandler.checkRetryable() keeps track o
ive.apache.org>"
mailto:user@hive.apache.org>>
Date: Tuesday, September 22, 2015 at 1:32 PM
To: "user@hive.apache.org<mailto:user@hive.apache.org>"
mailto:user@hive.apache.org>>
Subject: Transaction deadlocks
Thread A…
"HiveServer2-Background-Pool: Thread-35&q
Thread A…
"HiveServer2-Background-Pool: Thread-35" #35 prio=5 os_prio=0
tid=0x7fd150e4 nid=0x2c97 runnable [0x7fd146e0a000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(Socke
