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

Antidote crashing when multi-DC overloaded in a multi-DC setting. #320

Open
aletomsic opened this issue Nov 14, 2017 · 2 comments
Open

Antidote crashing when multi-DC overloaded in a multi-DC setting. #320

aletomsic opened this issue Nov 14, 2017 · 2 comments
Labels

Comments

@aletomsic
Copy link
Contributor

Full trace in the file.
It looks like it is caused by attempting to read from an ets table that does not exist under the following config.

{recover_meta_data_on_start, true}
{enable_logging, false}

The error does not occur when setting both parameters to true or false.

The error occurs in the master branch and can be reproduced in a config with multiple DCs, running basho_bench executing transactions that update a large amount of objects (500 in my case)

multidcCrash.log

@bieniusa
Copy link
Contributor

Does it only happen with a large number of data?

@aletomsic
Copy link
Contributor Author

My guess is that, at least, the interDC must be saturated to see this happening.
The problem does not occur under moderated load (fewer updates).
So I guess not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants