Stress tests and changes to the load balancing code.

Author: Richard Park

sdk/messaging/azeventhubs/internal/eh/stress/scenarios-matrix.yaml

@@ -61,3 +61,7 @@ matrix:
       prefetch: 0
       verbose: ""
       sleepAfter: "5m"
+    multibalance:
+      testTarget: multibalance
+      rounds: 100
+      verbose: ""

sdk/messaging/azeventhubs/internal/eh/stress/stress.go

@@ -18,6 +18,7 @@ func main() {
 	}{
 		{name: "batch", fn: tests.BatchStressTester},
 		{name: "balance", fn: tests.BalanceTester},
+		{name: "multibalance", fn: tests.MultiBalanceTester},
 		{name: "processor", fn: tests.ProcessorStressTester},
 	}
 

sdk/messaging/azeventhubs/internal/eh/stress/templates/stress-test-job.yaml

@@ -22,7 +22,11 @@ spec:
         - >
           set -ex;
           mkdir -p "$DEBUG_SHARE";
+          {{if eq .Stress.testTarget "multibalance" }}
+          /app/stress "{{.Stress.testTarget}}" "-rounds" "{{.Stress.rounds}}" "{{.Stress.verbose}}" 2>&1 | tee -a "${DEBUG_SHARE}/{{ .Stress.Scenario }}-`date +%s`.log";
+          {{else}}
           /app/stress "{{.Stress.testTarget}}" "-rounds" "{{.Stress.rounds}}" "-prefetch" "{{.Stress.prefetch}}" "{{.Stress.verbose}}" "-sleepAfter" "{{.Stress.sleepAfter}}" 2>&1 | tee -a "${DEBUG_SHARE}/{{ .Stress.Scenario }}-`date +%s`.log";
+          {{end}}
       # Pulls the image on pod start, always. We tend to push to the same image and tag over and over again
       # when iterating, so this is a must.
       imagePullPolicy: Always