Rajeshbabu Chintaguntla
Rajeshbabu Chintaguntla
The test case failures are not related to this change. @taklwu could you please review the change. Thanks.
> Why change from throwing an exception to returning false? @Apache9 During the express upgrade as mentioned in comment [here]( https://issues.apache.org/jira/browse/HBASE-27698?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=17699552#comment-17699552 ) there is no way to to detect the...
> Thank you @chrajeshbabu. It seems the changes make sense from the upgrade viewpoint. On the other hand, if this rare scenario were to happen on a healthy 2.x cluster,...
@Apache9 will commit it if it's fine for you. Could you please confirm.
> to check whether the meta directory is already there and if it is, if we can make sure that this is an upgrading from 1.x(by trying to read something...
> then insert a record to the master region so we can skip scheduling the InitMetaProcedure. We can insert record but we may not know the state and location which...
> So I think it only needs we have a record in master region for meta, and do not need to know its state and location? > > And we...
@Apache9 I have tried your suggestion of creating put entry of meta table in master region which gets filled in regionstates and helps to avoid calling init meta procedure there...