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

Weird things happen once #active validators + #revoked validators = max_validators #1911

Closed
4 tasks
gamarin2 opened this issue Aug 2, 2018 · 3 comments
Closed
4 tasks
Labels

Comments

@gamarin2
Copy link
Contributor

gamarin2 commented Aug 2, 2018

Summary of Bug

After number of active validators+number of revoked validators = max_validators, some weird things start happening.

First problem, number of revoked validators should not count towards max_validators, as per #1888 (comment).

Second, it seems that after the aforementioned condition is met, some unbonded validator can't enter the active validator set anymore.

This is heavily related to #1888 (comment).

Steps to Reproduce

Meet the aforementioned condition. Then try to get an unbonded validator in the val set.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@gamarin2 gamarin2 changed the title Weird things happen after #active validators + #revoked validators = max_validators Weird things happen once #active validators + #revoked validators = max_validators Aug 2, 2018
@cwgoes
Copy link
Contributor

cwgoes commented Aug 10, 2018

I think this is just a symptom of duplicate store keys caused by #1839 not being updated when validators are jailed.

If we want to debug this further, we'll need to look at specific instances and specific transactions.

@rigelrozanski
Copy link
Contributor

I second @cwgoes - it sounds like it was the same root cause - I'd propose this issue get closed unless specific bug cases can be reproduced on the develop branch.

@gamarin2
Copy link
Contributor Author

gamarin2 commented Aug 10, 2018

Ok, closing for now. Will reopen if issue shows up on upcoming testnets

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