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

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell edited comment on PHOENIX-1658 at 2/13/15 10:00 PM:
-------------------------------------------------------------------

This can also happen after a split without the user explicitly moving the region. I think there is a chance both cases can be handled the same way, on the master. 


was (Author: apurtell):
This can also happen after a split without the user explicitly moving the region. I think both cases can be handled the same way.

> 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)