[
https://issues.apache.org/jira/browse/PHOENIX-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby updated PHOENIX-5951:
-------------------------------------
Attachment: PHOENIX-5951-4.x.v4.patch
> IndexTool output logging for past-max-lookback rows should be configurable
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5951
> URL: https://issues.apache.org/jira/browse/PHOENIX-5951
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
> Attachments: PHOENIX-5951-4.x.v1.patch, PHOENIX-5951-4.x.v2.patch,
> PHOENIX-5951-4.x.v3.patch, PHOENIX-5951-4.x.v4.patch
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> On a global mutable table with lots of writes, it can be possible for there
> to be many rows flagged by index verification as invalid that are older than
> the max lookback age. These are likely due to race conditions between
> compaction in the base table and index table, but they can possibly show real
> issues.
> Since heavy output logging to PHOENIX_INDEX_TOOL can cause hotspotting, some
> operators may want to turn it off for this class of failures, while still
> wanting output logging for other kinds of invalid rows.
> As part of this change, we should start including in the output row a column
> with a code identifying the type of error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
