Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Replicator read model takes a lot of resources during replication of big event store (5kk events) #1949

Closed
pavsenin opened this issue Jul 14, 2021 · 1 comment
Assignees
Labels
bug Issues related to defects and incorrect/unexpected feature behavior severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc.

Comments

@pavsenin
Copy link

Describe the bug
The Replicator read model takes a lot of resources during replication of big event store (5kk events)

To Reproduce
Deploy replicator readmodel for big event store.

There are a lot of errors:
x0f8ha canceling statement due to statement timeout error 1,141
x0f8ha Query read timeout Error 611

99.9% "AWS/RDS", "CPUUtilization"

  • ReSolve Version 0.31.3
@MrCheater MrCheater added the bug Issues related to defects and incorrect/unexpected feature behavior label Jul 14, 2021
@MrCheater MrCheater added the severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc. label Jul 14, 2021
@MrCheater MrCheater assigned MrCheater and unassigned IhostVlad Sep 23, 2021
@MrCheater
Copy link
Contributor

500.000 event - 51 minutes
PASS ./replication.test.ts (1143.975 s)
Replication
✓ should deploy replica application (210757 ms)
✓ should deploy origin application (1143975 ms)
✓ should replicate all events and secrets from origin to replica (3061882 ms)

5.000.000 event ~ 8 hours and 30 minutes
I am waiting for the completion of the task "Resolve Gate"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues related to defects and incorrect/unexpected feature behavior severity: major Issues with high impact on the product, e.g., new packages, installation issues, etc.
Projects
None yet
Development

No branches or pull requests

3 participants