Improve reshard_collection_atlas_log_ingestion.js to Fail in Each Phase

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ClusterScalability Apr28-May09, ClusterScalability May12-May25, ClusterScalability Jun9-Jun23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Right now, reshard_collection_atlas_log_ingestion.js only has cases to verify that logs look correct when resharding fails during cloning and when it succeeds. Also verify that metrics are reported properly if it fails during other phases.

        1.
        		 Add Failpoint to Make Resharding Recipient Fail in Phase and Update reshard_collection_atlas_log_ingestion.js to Use It SERVER-104709 Sub-task Closed Brett Nawrocki 8.2.0-rc0
        2.
        		 reshard_collection_atlas_log_ingestion.js Fails in AwaitingFetchTimestamp SERVER-105353 Sub-task Blocked Brett Nawrocki  
        3.
        		 reshard_collection_atlas_log_ingestion.js Fails in CreatingCollection SERVER-105355 Sub-task In Progress Brett Nawrocki  
        4.
        		 reshard_collection_atlas_log_ingestion.js Fails in BuildingIndex SERVER-105356 Sub-task Open Brett Nawrocki  
        5.
        		 reshard_collection_atlas_log_ingestion.js Fails in Applying SERVER-105357 Sub-task Open Brett Nawrocki  

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: