[ https://issues.apache.org/jira/browse/HBASE-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704068#comment-15704068 ]
Josh Elser commented on HBASE-17187: ------------------------------------ bq. We are using the default num of retries only in the case where the exception is thrown is NOT a DNRIOE. Otherwise, we do not retry. The Phoenix test failure is throwing DNRIOE I think. Oh superb. My brain was expecting to see something in ClientScanner for that and ignored the server-side change :) +1 from me, for what it's worth :P > DoNotRetryExceptions from coprocessors should bubble up to the application > -------------------------------------------------------------------------- > > Key: HBASE-17187 > URL: https://issues.apache.org/jira/browse/HBASE-17187 > Project: HBase > Issue Type: Bug > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Attachments: hbase-17187_v1.patch > > > In HBASE-16604, we fixed a case where scanner retries was causing the scan to > miss some data in case the scanner is left with a dirty state (like a > half-seeked KVHeap). > The patch introduced a minor compatibility issue, because now if a > coprocessor throws DNRIOE, we still retry the ClientScanner indefinitely. > The test {{ServerExceptionIT}} in Phoenix is failing because of this with > HBASE-16604. -- This message was sent by Atlassian JIRA (v6.3.4#6332)