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

ASF GitHub Bot commented on CRAIL-8:
------------------------------------

GitHub user patrickstuedi opened a pull request:

    https://github.com/apache/incubator-crail/pull/4

    DataNodeInfo.key() was not updated when the object got updated, this is

    fixed now.
    
    https://issues.apache.org/jira/browse/CRAIL-8

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/patrickstuedi/incubator-crail multidatanode

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-crail/pull/4.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4
    
----
commit bc4cf76fadf573eafeac6bd8ff58ad468eba9050
Author: Patrick Stuedi <stu@...>
Date:   2018-02-22T15:59:08Z

    DataNodeInfo.key() was not updated when the object got updated, this is
    fixed now.
    
    https://issues.apache.org/jira/browse/CRAIL-8

----


> Make sure DataNodeInfo.key is invalidated on object updates
> -----------------------------------------------------------
>
>                 Key: CRAIL-8
>                 URL: https://issues.apache.org/jira/browse/CRAIL-8
>             Project: Apache Crail
>          Issue Type: Bug
>            Reporter: Patrick Stuedi
>            Priority: Major
>
> DataNodeInfo.key currently not being re-computed when the object is updated, 
> which in some cases results in read/write operations using only a subset of 
> the datanodes available in the cluster.



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

Reply via email to