Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-17043

CircleCI dtest multiplexer with MIDRES needs more resources

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      The CircleCI jobs for regular dtests jobs have more resources in MIDRES, which is necessary for some dtests to reliably success. However, the dtest multiplexer uses the same resources for LOWRES and MIDRES.

      I think that the dtest multiplexer should always use the same resources as the regular dtests. Using too small resources in the multiplexer can lead to failures that don't reproduce in the regular dtest jobs, like the one we found in CASSANDRA-16334 when trying to repeatedly run a resource-hungry dtest, or like this other one while running test_network_topology.

      This happens because I forgot to update the diff patch when adding the multiplexer. This doesn't affect HIGHRES because in that case the patch changes the configuration of the test executor, while in MIDRES a new executor is defined.

       

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            adelapena Andres de la Peña Assign to me
            adelapena Andres de la Peña
            Andres de la Peña
            Ekaterina Dimitrova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment