phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-4055) Consider IndexFailurePolicy before throwing when lock cannot be gotten
Date Mon, 31 Jul 2017 17:57:00 GMT
James Taylor created PHOENIX-4055:
-------------------------------------

             Summary: Consider IndexFailurePolicy before throwing when lock cannot be gotten
                 Key: PHOENIX-4055
                 URL: https://issues.apache.org/jira/browse/PHOENIX-4055
             Project: Phoenix
          Issue Type: Bug
            Reporter: James Taylor


We shouldn't necessarily be throwing in Indexer.preBatchMutateWithExceptions when we cannot
acquire a lock, since we're essentially failing the data write because we can't do the locking
necessary for performing consistent index maintenance. We'd ideally want to go through the
IndexFailurePolicy to determine whether or not we swallow that exception. We currently cannot
ignore this lock failure as we lack the ability to keep state between batch mutation coprocessor
calls (HBASE-18127).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message