[jira] [Updated] (HBASE-18457) [HLC] Follow up work of updating clocks on assign/unassign (duplicate)
[ https://issues.apache.org/jira/browse/HBASE-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-18457: - Summary: [HLC] Follow up work of updating clocks on assign/unassign (duplicate) (was: [HLC] Follow up work of updating clocks on assign/unassign) > [HLC] Follow up work of updating clocks on assign/unassign (duplicate) > -- > > Key: HBASE-18457 > URL: https://issues.apache.org/jira/browse/HBASE-18457 > Project: HBase > Issue Type: Sub-task >Reporter: Appy > > So list of things that need to be considered in future > - Mocking clocks in HMaster/RegionServer to test that clocks get updated on > assign/unassign > - Discuss the idea of adding timestamp type to NodeTime proto --> Get rid of > isLikelyOfType() fn > - In assign/unassign RPCs, either update the clock which matches table's > clock type OR all clocks. Updating only meta clock every time looks kind of > weird right now (and this called out explicitly in comments too). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18457) [HLC] Follow up work of updating clocks on assign/unassign
[ https://issues.apache.org/jira/browse/HBASE-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-18457: - Summary: [HLC] Follow up work of updating clocks on assign/unassign (was: [HLC] Follow up work of updating clocks (from HBASE-18395)) > [HLC] Follow up work of updating clocks on assign/unassign > -- > > Key: HBASE-18457 > URL: https://issues.apache.org/jira/browse/HBASE-18457 > Project: HBase > Issue Type: Sub-task >Reporter: Appy > > So list of things that need to be considered in future > - Mocking clocks in HMaster/RegionServer to test that clocks get updated on > assign/unassign > - Discuss the idea of adding timestamp type to NodeTime proto --> Get rid of > isLikelyOfType() fn > - In assign/unassign RPCs, either update the clock which matches table's > clock type OR all clocks. Updating only meta clock every time looks kind of > weird right now (and this called out explicitly in comments too). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
