Skip to content
This repository has been archived by the owner on Oct 7, 2023. It is now read-only.

Document -oracle vs -bridge options? #21

Closed
wrouesnel opened this issue Feb 25, 2017 · 2 comments
Closed

Document -oracle vs -bridge options? #21

wrouesnel opened this issue Feb 25, 2017 · 2 comments
Milestone

Comments

@wrouesnel
Copy link
Contributor

Neither of these two options are really documented by their command line help nor anywhere else I can see at the moment. Is there a clearer explanation of what they do?

@heyitsanthony
Copy link
Contributor

They're debugging features meant for comparing zetcd responses against zookeeper responses. If you don't know what they do, you probably don't need them. They should probably be prefixed with --debug- to make that more obvious...

@heyitsanthony
Copy link
Contributor

I realized I didn't provide an explanation but you may be interested regardless:

-zkbridge is the client address of what is considered a 'bonafide' zookeeper server (this can be a zetcd server too, but usually it's an actual zk server). It is used for cross checking when -oracle is given (comparing two server responses in lock-step) and testing protocol serialization/deserialization otherwise (zetcd will act as a proxy that will forward requests to another zk server).

-oracle accepts either etcd or zk; this chooses between treating the zetcd responses as ground truth or the zkbridge as ground truth when cross-checking. This is mostly important for selecting which server response to return in cases where the zetcd result can't reasonably be expected to perfectly match a zk response (e.g., znode mtime).

@heyitsanthony heyitsanthony added this to the v0.0.1 milestone Apr 10, 2017
heyitsanthony pushed a commit to heyitsanthony/zetcd that referenced this issue May 3, 2017
heyitsanthony pushed a commit to heyitsanthony/zetcd that referenced this issue May 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants