-
Notifications
You must be signed in to change notification settings - Fork 59
feat(bulk-load): meta server send bulk load request #457
Conversation
return; | ||
} | ||
|
||
broadcast_group_bulk_load(request); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whether broadcast_group_bulk_load
success or not doesn't influence response
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- meta -> primary: send bulk _load_request
- primary -> secondary: send group_bulk_load_request (through broadcast_group_bulk_load)
- secondary -> primary : report bulk load state (in group_bulk_load_response)
- primary -> meta: report group bulk load states (in bulk_load_response)
meta receives bulk_load_response, get group bulk load states, if bulk load is not finished, meta will resend bulk _load_request to primary.
If broadcast_group_bulk_load
failed, the states in response reported to meta may not fresh. However, it is ok, meta will resend request and finally get the states. Besides, broadcasting group bulk load is not a synchronous process, the states in response will not always be fresh.
This pull request is about meta server send bulk_load_request to replica server.
partition_bulk_load
on_bulk_load
when receive bulk_load_requestdo_bulk_load
- not implemented in this pr )broadcast_group_bulk_load
,report_bulk_load_states_to_meta
- not implemented in this pr)on_partition_bulk_load_reply
when receive bulk_load_response, also not implemented in this pr.Whole bulk load process document can be found in official website: bulk_load_design