-
Notifications
You must be signed in to change notification settings - Fork 4
PCSM-167 Updated the pcsm status output #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -146,36 +146,37 @@ | |
| | `state` | string | Current replication state | | ||
| | `info` | string | Additional information about the current state| | ||
| | `error`| string | (optional): The error message if the operation failed. | ||
| | `lagTime` | number | Current lag time in logical seconds between source and target clusters. | | ||
| | `eventsProcessed` | number | Total events processed | | ||
| | `lastReplicatedOpTime` | string | The last replicated operation time.| | ||
| | `lagTimeSeconds` | number | Current lag time in logical seconds between source and target clusters. | | ||
| | `eventsRead` | number | Total number of events read from the source | | ||
| | `eventsApplied` | number | Total number of events applied to the target | | ||
| | `lastReplicatedOpTime` | string | The last replicated operation time. It includes both the time stamp and its human-readable representation | | ||
| | `initialSync.completed` | boolean | Initial sync completion status | | ||
| | `initialSync.lagTime` | number | The lag time in logical seconds until the initial sync completed| | ||
|
||
| | `initialSync.cloneCompleted` | boolean | Clone process completion status | | ||
| | `initialSync.estimatedCloneSize` | number | Estimated total size to clone (bytes) | | ||
| | `initialSync.clonedSize` | number | Current cloned size (bytes) | | ||
| | `initialSync.estimatedCloneSizeBytes` | number | Estimated total size to clone (bytes) | | ||
|
Check notice on line 156 in docs/api.md
|
||
| | `initialSync.clonedSizeBytes` | number | Current cloned size (bytes) | | ||
|
Check notice on line 157 in docs/api.md
|
||
|
|
||
|
|
||
| Example: | ||
|
|
||
| ```json | ||
| { | ||
| "ok": true, | ||
| "state": "running", | ||
| "info": "Initial Sync", | ||
|
|
||
| "lagTime": 22, | ||
| "eventsProcessed": 5000, | ||
| "lastReplicatedOpTime": "1740335200.5", | ||
|
|
||
| "initialSync": { | ||
| "completed": false, | ||
| "lagTime": 5, | ||
|
|
||
| "cloneCompleted": false, | ||
| "estimatedCloneSize": 5000000000, | ||
| "clonedSize": 2500000000 | ||
| } | ||
| "ok": true, | ||
| "state": "running", | ||
| "info": "Replicating Changes", | ||
| "lagTimeSeconds": 1, | ||
| "eventsRead": 0, | ||
| "eventsApplied": 0, | ||
| "lastReplicatedOpTime": { | ||
| "ts": "1763649865.1", | ||
| "isoDate": "2025-11-20T14:44:25Z" | ||
| }, | ||
| "initialSync": { | ||
| "estimatedCloneSizeBytes": 24220000, | ||
| "clonedSizeBytes": 24220000, | ||
| "completed": true, | ||
| "cloneCompleted": true | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
|
|
||
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.
The type is documented as 'string' but the example shows it as an object with 'ts' and 'isoDate' fields. Update the type to 'object' to match the actual structure.
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.
What do you think that we add
tsandisoDatefields as separate, likelastReplicatedOpTime.tslastReplicatedOpTime.isoDateJust like we have for
initialSyncobject.