You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the first object send to timestream this error pops up. This one popped up on ap-northeast-2 data aggregator.
This error is not replicated on the aggregator @ sa-east-1 where there is only one container up. So this appears to be an issue because it is receiving information from multiple containers.
Highly recommend doing a single remote region with 3000 to even 20000 VUs to see how the aggregator fares.
Overview
ap-northeast-2
data aggregator.sa-east-1
where there is only one container up. So this appears to be an issue because it is receiving information from multiple containers.Tested against config:
Tested against test script:
In

ap-northeast-2
- 15 testers - 1 aggregatorI am guessing that normal operations refer to just no objects received (ie: waiting to receive info from test engine)
But this shows that the first object sent to timestream fails

In
sa-east-1
, 1 tester - 1 aggregatorThe text was updated successfully, but these errors were encountered: