etcd watch process should handle 401 error #30
Labels
Comments
nati
added a commit
that referenced
this issue
Nov 9, 2015
Closes: issue #30 Etcd can hold up to 1000 history, so we need to handle this case correctly. We have following issues. (1) We should clone env for each extension run by sync (2) sync.Watch API keep blocking even if we get 401. (3) Stop lock per resource In case we have more than 1000 resources, sync process do infinite loop because it increases etcd index by lock. (4) sync packages is using thread-unsafe map In this commit, we fix these issues, and we added simple integration test configuraion file.
nati
added a commit
that referenced
this issue
Nov 9, 2015
Closes: issue #30 Etcd can hold up to 1000 history, so we need to handle this case correctly. We have following issues. (1) We should clone env for each extension run by sync (2) sync.Watch API keep blocking even if we get 401. (3) Stop lock per resource In case we have more than 1000 resources, sync process do infinite loop because it increases etcd index by lock. (4) sync packages is using thread-unsafe map In this commit, we fix these issues, and we added simple integration test configuraion file.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
etcd watch process should handle 401 error.
What's happening in our env.
(1) resources more than 500 rows
(2) boot gohan
(3) state watch process will lock for each
(4) etcd stores up to 1000 history, so we lost some history and got 401 error
The text was updated successfully, but these errors were encountered: