Hi zhengrui.m, The OperationInitialize MetaLog entry is never supposed to be removed from the MetaLog once it has been run. By setting the approvals required to 2 (one more than the number of approvals that it receives), this prevents the OperationInitialize entry from getting removed from the MetaLog which prevents the system from re-initializing itself if it gets restarted.
- Doug On Mon, Dec 26, 2011 at 7:54 PM, zhengrui.m <[email protected]> wrote: > ** > hi all, > I learn the code of hypertable master.there are two operation that > inherit interface :remove_explicitly() and remove_approvals_required(). > They are: > OperationInitialize > OperationMoveRange > the OperationInitialize execute process maybe like this: > 1. RemovalManager::add_operation( OperationInitialize ) > 2. OperationProcessor call OperationInitialize::execute() > 3. if all dependency is ok.the OperationInitialize finish > 4. OperationProcessor:retire_operation(). > 5. RemvoalManager:approval_removal( OperationInitialize ) > while the > OperationInitialize::remove_approvals_required() return value 2. > so ,the RemvoalManager:approval_removal() must be call twice,to > finish the OperationInitialize in meta log > how another RemvoalManager:approval_removal happen? > > > ------------------------------ > zhengrui.m > > -- > You received this message because you are subscribed to the Google Groups > "Hypertable Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/hypertable-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en.
