You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 13:08:18 UTC

[jira] [Updated] (KUDU-706) java client "stuck" in YCSB against 100 nodes

     [ https://issues.apache.org/jira/browse/KUDU-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated KUDU-706:
----------------------------
    Parent: KUDU-435

> java client "stuck" in YCSB against 100 nodes
> ---------------------------------------------
>
>                 Key: KUDU-706
>                 URL: https://issues.apache.org/jira/browse/KUDU-706
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: Private Beta
>            Reporter: Todd Lipcon
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>         Attachments: stuck-after-heapdump.log
>
>
> I'm trying to run a 4-thread YCSB workload against a 100-node cluster. It very quickly got "stuck". The 4 threads are all waiting on some operation which is neither timing out nor responding. I looked at /transactionz and /rpcz across all the nodes and none seems to be doing anything. So, I think there's some kind of bug in the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)