-
Notifications
You must be signed in to change notification settings - Fork 25.8k
[CCR] Fetches/indexing/writes/reads/bulks in status fields vs readers in task params #34703
Copy link
Copy link
Closed
Closed
Copy link
Labels
:Distributed/CCRIssues around the Cross Cluster State Replication featuresIssues around the Cross Cluster State Replication featuresblockerv6.5.0
Description
The status reports for the following tasks often refer to fetches (number_of_successful_fetches,number_of_failed_fetches, total_fetch_time_millis,fetch_exceptions). We also have a similar term (which is identical in meaning) call reads (number_of_concurrent_reads). We also have the generic operations_received and total_transferred_bytes and last_requested_seq_no.
On the write sides we have bulk (number_of_successful_bulk_operations, number_of_failed_bulk_operations) and writes (number_of_concurrent_writes, number_of_queued_writes <-- note the different semantics here).
I think we should align our terminologies across the various places. I personally like the read versus write and bulk vs ops. Howabout:
number_of_succesful_bulk_readsnumber_of_failed_bulk_readstotal_bulk_read_timenumber_of_ongoing_bulk_readstotal_operations_readtotal_bytes_readlast_requested_seq_no_for_readsnumber_of_successful_bulk_writesnumber_of_failed_bulk_writesnumber_of_ongoing_bulk_writesnumber_of_queued_ops_to_write(not too happy with this one)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/CCRIssues around the Cross Cluster State Replication featuresIssues around the Cross Cluster State Replication featuresblockerv6.5.0
Type
Fields
Give feedbackNo fields configured for issues without a type.