You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2019/01/10 21:25:00 UTC

[jira] [Resolved] (KUDU-1535) Add rack awareness

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

Will Berkeley resolved KUDU-1535.
---------------------------------
       Resolution: Done
    Fix Version/s: 1.9.0

This is done besides some documentation.

The first iteration supports assigning locations to tablet servers and clients, enforcing that a placement policy that a majority of replicas is not placed in the same location/rack, rebalancing replicas to re-establish the placement policy, rebalancing for replica count compatible with the placement policy, and allowing clients to choose to scan preferentially from tablet servers in the same location.

> Add rack awareness
> ------------------
>
>                 Key: KUDU-1535
>                 URL: https://issues.apache.org/jira/browse/KUDU-1535
>             Project: Kudu
>          Issue Type: New Feature
>          Components: master
>            Reporter: Jean-Daniel Cryans
>            Assignee: Will Berkeley
>            Priority: Major
>             Fix For: 1.9.0
>
>
> Kudu currently doesn't have the concept of rack awareness, so any kind of rack failure can result in data loss (assuming that Kudu has tablet servers in multiple racks).
> This changes how the master picks hosts to send new tablets to, and we also need to implement a way for the master to map hostname names to racks (could be similar to Hadoop).



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