[SERVER-74546] Malformed data returned by the `checkMetadataConsistency` command Created: 02/Mar/23  Updated: 27/Oct/23  Resolved: 03/Mar/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

The command to check the sharding metadata consistency, i.e., checkMetadataConsistency, returns a list of malformed entries when it runs with the granularity of cluster-level.

Specifically, it seems that this test causes a metadata inconsistency, but the entry returned by the command is actually the string "0" (double-quote included) instead of a JSON containing detailed information on the detected inconsistency.



 Comments   
Comment by Antonio Fuschetto [ 03/Mar/23 ]

We quickly realized that the problem was due to how the metadata inconsistencies were iterated in JavaScript, i.e., using for...in instead of for...of.

Generated at Thu Feb 08 06:27:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.