[
https://issues.apache.org/jira/browse/PHOENIX-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208255#comment-14208255
]
James Taylor commented on PHOENIX-1434:
---------------------------------------
[~mujtaba] - Also, a unit test that repros this would be good - you'd need to
manually split and confirm that
!region.getRegionNameAsString().equals(Bytes.toBytes(region.getRegionName)). If
that's the case, then when you split that region, the parent region wouldn't
have been deleted. You can add that test to StatsCollectorIT, probably as part
of the existing test that manually splits. I'll create another JIRA for that.
> Stats are not maintained correctly through splits and/or compactions
> --------------------------------------------------------------------
>
> Key: PHOENIX-1434
> URL: https://issues.apache.org/jira/browse/PHOENIX-1434
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Mujtaba Chohan
> Attachments: PHOENIX-1434.patch
>
>
> We're seeing the number of regions the stats table thinks there are not being
> in agreement with the actual number of regions. It seems to be related to
> splits and compactions. In particular, when a split is occurring, the
> deletion of the stats for the region being split is not being deleted as
> expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
