hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Plamen Jeliazkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13665) Move RPC response serialization into Server.doResponse
Date Mon, 25 Jun 2018 16:46:00 GMT

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

Plamen Jeliazkov updated HDFS-13665:
------------------------------------
    Description: 
In HDFS-13399 we addressed a race condition in AlignmentContext processing where the RPC response
would assign a transactionId independently of the transactions own processing, resulting in
a stateId response that was lower than expected. However this caused us to serialize the RpcResponse
twice in order to address the header field change.

See here:
https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16464279&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16464279

And here:
https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16498660&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16498660

At the end it was agreed upon to move the logic of Server.setupResponse into Server.doResponse
directly.

  was:
In HDFS-13399 we addressed a race condition in AlignmentContext processing where the RPC response
would assign a transactionId independently of the transactions own processing, resulting in
a stateId response that was lower than expected.

See here:
https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16464279&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16464279

And here:
https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16498660&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16498660

At the end it was agreed upon to move the logic of Server.setupResponse into Server.doResponse
directly.


> Move RPC response serialization into Server.doResponse
> ------------------------------------------------------
>
>                 Key: HDFS-13665
>                 URL: https://issues.apache.org/jira/browse/HDFS-13665
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Plamen Jeliazkov
>            Assignee: Plamen Jeliazkov
>            Priority: Major
>
> In HDFS-13399 we addressed a race condition in AlignmentContext processing where the
RPC response would assign a transactionId independently of the transactions own processing,
resulting in a stateId response that was lower than expected. However this caused us to serialize
the RpcResponse twice in order to address the header field change.
> See here:
> https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16464279&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16464279
> And here:
> https://issues.apache.org/jira/browse/HDFS-13399?focusedCommentId=16498660&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16498660
> At the end it was agreed upon to move the logic of Server.setupResponse into Server.doResponse
directly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message