Add information about using "p" dir coming from other Dgraph clusters… #384
Conversation
…#138) * added information about using p dirs coming from different Dgraph clusters * typos * Apply suggestions from code review * Update content/deploy/fast-data-loading/bulk-loader.md * Update content/deploy/fast-data-loading/bulk-loader.md * Update content/deploy/fast-data-loading/bulk-loader.md * Update content/deploy/fast-data-loading/bulk-loader.md * Update content/deploy/fast-data-loading/bulk-loader.md Co-authored-by: Damián Parrino <bucanero@users.noreply.github.com> Co-authored-by: aaroncarey <31550444+aaroncarey@users.noreply.github.com>
|
|
✅ Deploy Preview for dgraph-docs-repo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
| @@ -272,6 +272,46 @@ I1227 13:27:53.959671 29781 draft.go:571] Creating snapshot at index: 34. Read | |||
| ``` | |||
| Note that `snapshot at index` value must be the same within the same Alpha group and `ReadTs` must be the same value within and among all the Alpha groups. | |||
|
|
|||
| ### Using "p" directories coming from different Dgraph clusters | |||
There was a problem hiding this comment.
we should limit the width of the line. It simplifies future diff etc.
| After starting your Zero nodes, you need to increase the Zero's timestamp by sending the following `curl` request to the Zero leader node: | ||
|
|
||
| ``` | ||
| curl "zero_address:port/assign?what=timestamps&num=X" #with X = high number e.g. 100000 or higher |
There was a problem hiding this comment.
I am not sure if having vague numbers is a good idea. Maybe @rderbier has an opinion here.
| Now you need to confirm whether this timestamp has been increased as expected. You can do this by sending a `curl` request to the zero `/state` endpoint, as follows: | ||
|
|
||
| ``` | ||
| curl zero-address:port/state | jq |
There was a problem hiding this comment.
we should specify the port here.
| ``` | ||
| curl zero-address:port/state | jq | ||
| ``` | ||
| At the end of the response, look for the value shown for `"maxTxnTs"`. This value should be greater than or equal to the timestamp you assigned in the previous `curl` request, as shown in the following example: |
There was a problem hiding this comment.
what do we do if timestamp is not greater?
There was a problem hiding this comment.
I haven't thoroughly reviewed each cherry-picked change in the content; I only checked if they align with the main branch at a basic level. If you'd like to make any modifications, please feel free to push commits to the branch. Since this was a cherry-pick, I didn't have plans to work on the content myself. It was requested that I examine whether it could be incorporated into the main branch. Given that this is an older cherry-pick that was validated by the previous docs team, I don't see a reason to refactor their content. However, if you feel otherwise, go ahead and push your commits.
This pr explains how to properly use a
pdirectory that is coming from a different cluster. This adds instruction on how to let Zero correctly manage thepdirectory by increasing the timestamp