[ https://issues.apache.org/jira/browse/HBASE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Trezzo updated HBASE-6170: -------------------------------- Attachment: HBASE-6170v2.patch @Ted. Thanks for the reply! I have corrected the comment in HRegionServer. Regarding your second comment, I am not sure I see the need to switch getInt back to getLong. Internally, the timeout value is treated as an int. There is a hidden potential for precision loss if a client uses a long in the config file. Changing everything to getInt removes the cast and makes the internal/external representation of the timeout period consistent. Going forward, if we decide that the extra bits in a long are needed (i.e. a use case that requires timeout periods longer than 24 days), existing configurations will not be broken and the switch to longs will require minimal code changes. > Timeouts for row lock and scan should be separate > ------------------------------------------------- > > Key: HBASE-6170 > URL: https://issues.apache.org/jira/browse/HBASE-6170 > Project: HBase > Issue Type: Improvement > Components: regionserver > Affects Versions: 0.94.0 > Reporter: Otis Gospodnetic > Assignee: Chris Trezzo > Priority: Minor > Fix For: 0.96.0 > > Attachments: HBASE-6170v1.patch, HBASE-6170v1.patch, > HBASE-6170v1.patch, HBASE-6170v2.patch > > > Apparently the timeout used for row locking and for scanning is global. It > would be better to have two separate timeouts. > (opening the issue to make Lars George happy) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira