You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2020/06/11 17:34:00 UTC

[jira] [Created] (PHOENIX-5951) IndexTool output logging for invalid past-max-lookback rows should be configurable

Geoffrey Jacoby created PHOENIX-5951:
----------------------------------------

             Summary: IndexTool output logging for invalid 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


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)