[
https://issues.apache.org/jira/browse/HBASE-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126311#comment-16126311
]
Appy commented on HBASE-18457:
------------------------------
All of the work got done as part of other jiras:
- Mocking clocks in HMaster/RegionServer to test that clocks get updated on
assign/unassign - HBASE-18395
- Discuss the idea of adding timestamp type to NodeTime proto - HBASE-18497
- 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). - HBASE-18497 makes
the change to send all clocks with the RPC.
Closing this jira as duplicate.
> [HLC] Follow up work of updating clocks (from HBASE-18395)
> ----------------------------------------------------------
>
> 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)
