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

Posted to dev@phoenix.apache.org by "Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org> on 2015/02/13 10:59:12 UTC

[jira] [Updated] (PHOENIX-1658) Automatically move data/index region when corresponding local index/data region is moved explicitly from client

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

Rajeshbabu Chintaguntla updated PHOENIX-1658:
---------------------------------------------
    Summary: Automatically move data/index region when corresponding local index/data region is moved explicitly from client  (was: Automatically move data/index region when corresponding region is moved explicitly)

> Automatically move data/index region when corresponding local index/data region is moved explicitly from client
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1658
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1658
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.0.0
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>
> Currently when a region moved explicitly from client then corresponding index/data region wont be moved. So we may see colocation mismatches till balancer triggered again. We can move the corresponding region in post move hook so there won't be colocation mismatches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)