[
https://issues.apache.org/jira/browse/PHOENIX-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670823#comment-16670823
]
Geoffrey Jacoby commented on PHOENIX-5002:
------------------------------------------
[~vincentpoon] - I was curious how the clients pick up metadata changes, to see
if there were potential gaps where index updates could be missed.
Either we were:
1. Caching the PTables, in which case we could be stale at the time we
determine whether an index exists and is online or not when setting up the
MutationState. OR
2. Looking up the PTables each time, in which case we have to hit
System.Catalog for _every_ commit, which has some concerning perf and
robustness implications.
After digging through the code, it appears to be Option 2: MutationState#send
calls MutationState#validateAll which refreshes metadata.
> Don't load or disable Indexer coprocessor for non-indexed tables
> ----------------------------------------------------------------
>
> Key: PHOENIX-5002
> URL: https://issues.apache.org/jira/browse/PHOENIX-5002
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.14.1
> Reporter: Vincent Poon
> Priority: Major
>
> It seems the Indexer coprocessor is loaded for tables even if they have no
> indexes.
> There is some overhead such as write locking within Phoenix - we should
> investigate whether we can avoid loading the Indexer coproc or disable it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
