nsqd: OOM when misconfiguring lookupd addresses #615
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.
Hi there,
I've been reconfiguring our deploy getting ready to launch our product and have been hitting brick wall after brick wall with an out of memory issue. At first I thought it was an issue with my VPC configuration so I created a clean instance and succeeded (with and without docker) to reproduce the issue.
It might be something Amazon has done lately with their AMI images, but everything was working fine a few weeks ago so wanted to check in and see if it's anything on your end.
Steps to reproduce
wget https://s3.amazonaws.com/bitly-downloads/nsq/nsq-0.3.5.linux-amd64.go1.4.2.tar.gz && tar zxvf nsq-0.3.5.linux-amd64.go1.4.2.tar.gz
nsqlookupd
- everything looks and smells finensqd -lookupd-tcp-address=127.0.0.1:4161
- and I get the followingI realise this could well be operator error but I'd appreciate a prod in the right direction - been banging my head against this all day.
Cheers