[
https://issues.apache.org/jira/browse/KUDU-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075762#comment-16075762
]
Todd Lipcon commented on KUDU-2053:
-----------------------------------
I had one theory that this was due to the Spark code stressing multiple
KuduSession objects with the same KuduClient, but I tried writing an
integration test for that and couldn't repro. I'll post that test anyway, and
keep hunting.
> Request reported as stale by the server in the spark client
> -----------------------------------------------------------
>
> Key: KUDU-2053
> URL: https://issues.apache.org/jira/browse/KUDU-2053
> Project: Kudu
> Issue Type: Bug
> Components: java
> Affects Versions: 1.3.0
> Reporter: David Alves
> Priority: Critical
>
> We had multiple reports of requests being reported as stale by the server
> when using the spark client. Writes fail with an error like:
> [Peer xxx] Tablet server sent error Incomplete: Request with id { client_id:
> "11ef08bf559a49568e607fe3a616cc51" seq_no: 1 first_incomplete_seq_no: 1
> attempt_no: 1 } is stale.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)