consumer: resolved addresses and reconnects #111
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
nsq_to_nsq unexpectedly quit, and I have copious logs:
nsq_to_nsq run file:
nsqd run file:
nsq_to_nsq logs:
nsqd logs:
Initially, the destination nsqd was unreachable, but it did become reachable towards the end of the logs and this is visible with
06:36:09 INF 2 (this.is.a.cname.net:543) connecting to nsqd
. However, after becoming reachable, nsq_to_nsq noped right out of sending messages and stopped.@jehiah thinks "there might be a subtle detail there with it using the resolved address in one spot an the hostname in another"
specifically here: https://github.com/bitly/go-nsq/blob/cfa41b99b4efed4f19d990d6d1eb60f0e30a4062/consumer.go#L766