[jira] [Comment Edited] (HBASE-2161) get rid of scanner timeout
[
https://issues.apache.org/jira/browse/HBASE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268063#comment-14268063
]
ryan rawson edited comment on HBASE-2161 at 1/7/15 7:27 PM:
¯\\_(ツ)_/¯
was (Author: ryanobjc):
¯\_(ツ)_/¯
get rid of scanner timeout
--
Key: HBASE-2161
URL: https://issues.apache.org/jira/browse/HBASE-2161
Project: HBase
Issue Type: Bug
Reporter: ryan rawson
Labels: delete
the client side code has this in ClientScanner.next():
if (e instanceof UnknownScannerException
lastNext + scannerTimeout System.currentTimeMillis()) {
ScannerTimeoutException ex = new ScannerTimeoutException();
ex.initCause(e);
throw ex;
}
This will cause the client-side to timeout after the 'scannerTimeout'. There
doesn't seem to be any good reason for this - we can just restart the scanner
at the last row. Leave the server-side scanner as is, but clients should be
able to have a 5 day scan that is continuously being restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-2161) get rid of scanner timeout
[
https://issues.apache.org/jira/browse/HBASE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268063#comment-14268063
]
ryan rawson edited comment on HBASE-2161 at 1/7/15 7:27 PM:
¯\_(ツ)_/¯
was (Author: ryanobjc):
¯\\_(ツ)_/¯
get rid of scanner timeout
--
Key: HBASE-2161
URL: https://issues.apache.org/jira/browse/HBASE-2161
Project: HBase
Issue Type: Bug
Reporter: ryan rawson
Labels: delete
the client side code has this in ClientScanner.next():
if (e instanceof UnknownScannerException
lastNext + scannerTimeout System.currentTimeMillis()) {
ScannerTimeoutException ex = new ScannerTimeoutException();
ex.initCause(e);
throw ex;
}
This will cause the client-side to timeout after the 'scannerTimeout'. There
doesn't seem to be any good reason for this - we can just restart the scanner
at the last row. Leave the server-side scanner as is, but clients should be
able to have a 5 day scan that is continuously being restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-2161) get rid of scanner timeout
[
https://issues.apache.org/jira/browse/HBASE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268063#comment-14268063
]
ryan rawson edited comment on HBASE-2161 at 1/7/15 7:27 PM:
{{ ¯\_(ツ)_/¯}}
was (Author: ryanobjc):
¯\_(ツ)_/¯
get rid of scanner timeout
--
Key: HBASE-2161
URL: https://issues.apache.org/jira/browse/HBASE-2161
Project: HBase
Issue Type: Bug
Reporter: ryan rawson
Labels: delete
the client side code has this in ClientScanner.next():
if (e instanceof UnknownScannerException
lastNext + scannerTimeout System.currentTimeMillis()) {
ScannerTimeoutException ex = new ScannerTimeoutException();
ex.initCause(e);
throw ex;
}
This will cause the client-side to timeout after the 'scannerTimeout'. There
doesn't seem to be any good reason for this - we can just restart the scanner
at the last row. Leave the server-side scanner as is, but clients should be
able to have a 5 day scan that is continuously being restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-2161) get rid of scanner timeout
[
https://issues.apache.org/jira/browse/HBASE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268063#comment-14268063
]
ryan rawson edited comment on HBASE-2161 at 1/7/15 7:27 PM:
¯\_(ツ)_/¯
was (Author: ryanobjc):
{{ ¯\_(ツ)_/¯}}
get rid of scanner timeout
--
Key: HBASE-2161
URL: https://issues.apache.org/jira/browse/HBASE-2161
Project: HBase
Issue Type: Bug
Reporter: ryan rawson
Labels: delete
the client side code has this in ClientScanner.next():
if (e instanceof UnknownScannerException
lastNext + scannerTimeout System.currentTimeMillis()) {
ScannerTimeoutException ex = new ScannerTimeoutException();
ex.initCause(e);
throw ex;
}
This will cause the client-side to timeout after the 'scannerTimeout'. There
doesn't seem to be any good reason for this - we can just restart the scanner
at the last row. Leave the server-side scanner as is, but clients should be
able to have a 5 day scan that is continuously being restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
