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

Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2017/08/25 21:23:00 UTC

[jira] [Commented] (KUDU-582) Send TS specific errors back to the client when the client is supposed to take specific actions, such as trying another replica

    [ https://issues.apache.org/jira/browse/KUDU-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142224#comment-16142224 ] 

Jean-Daniel Cryans commented on KUDU-582:
-----------------------------------------

Hey [~dr-alves], what should we do with this jira? It feels ancient and not that well defined. Should we close?

> Send TS specific errors back to the client when the client is supposed to take specific actions, such as trying another replica
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KUDU-582
>                 URL: https://issues.apache.org/jira/browse/KUDU-582
>             Project: Kudu
>          Issue Type: Bug
>          Components: client, consensus, tserver
>    Affects Versions: M4.5
>            Reporter: David Alves
>            Priority: Critical
>
> Right now we're sending umbrella statuses that the client is supposed to interpret as a command that it should failover to another replica. This is misusing statuses but it's also a problem in that we're likely (or will likely) sending the same statuses (illegal state and abort) in places where we don't mean the client to failover.
> This should be treated holistically in both clients and in the server components.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)