Skip to content

DA Errors - RejectedRecordsException #54

Description

@neebs12

Overview

Lists issues encountered with Data Aggregator

  • RejectedRecordsException
    • 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.

Tested against config:

{
  "DURATION": 20000,
  "HOME_REGION": "us-east-1",
  "REMOTE_REGIONS": {
    "ap-northeast-1": 1001,
    "us-east-2": 2001,
    "us-west-1": 3001,
    "ap-south-1": 1000,
    "sa-east-1": 100,
    "ap-northeast-2": 3000
  }
}

Tested against test script:

"use strict";

const sleep = async (ms) => {
  return new Promise((resolve) => {
    setTimeout(resolve, ms);
  });
};

export const script = async (axiosInstance) => {
  await axiosInstance.post(
    "https://mockbin.org/bin/19b03afc-cdb8-4ddd-b545-840f10851db0",
    {
      timeStamp: Date.now(),
    }
  );
  await sleep(500);
  await axiosInstance.get(
    "https://mockbin.org/bin/19b03afc-cdb8-4ddd-b545-840f10851db0"
  );
  await sleep(500);
};
  • In ap-northeast-2 - 15 testers - 1 aggregator
    Image

  • I 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
    Image

  • In sa-east-1, 1 tester - 1 aggregator

  • Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions