[
https://issues.apache.org/jira/browse/PHOENIX-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118113#comment-14118113
]
rajeshbabu commented on PHOENIX-1200:
-------------------------------------
The reason for this slowness is because of compaction after splitting only.
Handling PHOENIX-1170 itself solves this problem.
> Delay setting local index active until usable
> ---------------------------------------------
>
> Key: PHOENIX-1200
> URL: https://issues.apache.org/jira/browse/PHOENIX-1200
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.1
> Reporter: James Taylor
> Assignee: rajeshbabu
>
> The performance of a local index immediately after it is built is terrible.
> Instead of taking 1 second over a count(*) query, it takes 9 seconds. This is
> an order of magnitude worse than a full scan over the data table. After some
> period of time, the performance is good.
> We should delay setting the local index as active until after whatever is
> going on finishes to prevent the local index from being used while it's so
> slow. First we need to figure out what HBase is doing at this point.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
