You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/10/12 22:10:20 UTC
[jira] [Resolved] (KUDU-954) Client can get stuck if the master
fails while setting up
[ https://issues.apache.org/jira/browse/KUDU-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved KUDU-954.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: n/a
haven't seen anything like this in over a year, let's assume it's not a problem
> Client can get stuck if the master fails while setting up
> ---------------------------------------------------------
>
> Key: KUDU-954
> URL: https://issues.apache.org/jira/browse/KUDU-954
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: Feature Complete
> Reporter: Jean-Daniel Cryans
> Fix For: n/a
>
>
> This happened after we enabled HybridClock but before we upped the max error, the client got stuck there for days:
> {noformat}
> Thread 1 (Thread 0x7f1ef2310860 (LWP 25576)):
> #0 0x000000377b00b43c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
> #1 0x000000000072d6c0 in kudu::client::KuduClient::Data::SetMasterServerProxy(kudu::client::KuduClient*, kudu::MonoTime const&) ()
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)