You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
data_path="/var/lib/nsq/"http_address="127.0.0.1:2151"tcp_address="0.0.0.0:2150"nsqlookupd_tcp_addresses="127.0.0.1:4160"sync_every=100# number of messages per diskqueue fsyncmem_queue_size=200000msg_timeout="10s"
node 2
data_path="/var/lib/nsq/"http_address="127.0.0.1:2251"tcp_address="0.0.0.0:2250"nsqlookupd_tcp_addresses="127.0.0.1:4160"sync_every=100# number of messages per diskqueue fsyncmem_queue_size=200000msg_timeout="10s"
cosumer logs grep in /tmp/2.log as we can see as below, there're errors says "ID not in flight".
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e4491335b0d004 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e4491335b0d003 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e449133770d003 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e449133770d004 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e449133770d005 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2150) protocol error - E_FIN_FAILED FIN 08e449133770d006 failed ID not in flight
ERR 1 [test_topic/chn_x1] (chaos-hot.local:2250) protocol error - E_FIN_FAILED FIN 08e449144ef0d005 failed ID not in flight
server side(nsqd) logs grep 08e449144ef0d005 /tmp/3.log check the following. The message ID "08e449144ef0d005" was assigned to two different messages (we can see that the message bodies are different). So the "FIN" command for the second message were to be failed.
[nsqd] 2015/09/07 11:03:33.311022 PROTOCOL(V2): writing msg(08e449144ef0d005) to client(127.0.0.1:55167) - TestMessageBlaBla:1441593906.8762381076812744
[nsqd] 2015/09/07 11:03:33.311144 PROTOCOL(V2): writing msg(08e449144ef0d005) to client(127.0.0.1:55167) - TestMessageBlaBla:1441593906.8771169185638428
[nsqd] 2015/09/07 11:03:33.311382 PROTOCOL(V2): [127.0.0.1:55167] [FIN 08e449144ef0d005]
[nsqd] 2015/09/07 11:03:33.311438 PROTOCOL(V2): [127.0.0.1:55167] [FIN 08e449144ef0d005]
[nsqd] 2015/09/07 11:03:33.311456 ERROR: [127.0.0.1:55167] - E_FIN_FAILED FIN 08e449144ef0d005 failed ID not in flight - ID not in flight
6. Versions
Go: go version go1.5 darwin/amd64
nsq: nsqd v0.3.6-alpha (built w/go1.5); git revision: 1746cc6
The text was updated successfully, but these errors were encountered:
Steps
1. Consumer code
2. NSQD configuration
node 1
node 2
3. start NSQD
GOMAXPROCS=5 nsqd -config=/etc/nsq/node-1.conf -max-rdy-count 10000 -verbose 2>/tmp/3.log
GOMAXPROCS=5 nsqd -config=/etc/nsq/node-2.conf -max-rdy-count 10000 -verbose 2>/tmp/3.log
4. Start consumer and run for a while
./consumer
5. check logs
cosumer logs
grep in /tmp/2.log
as we can see as below, there're errors says "ID not in flight".
server side(nsqd) logs
grep 08e449144ef0d005 /tmp/3.log
check the following. The message ID "08e449144ef0d005" was assigned to two different messages (we can see that the message bodies are different). So the "FIN" command for the second message were to be failed.
6. Versions
Go: go version go1.5 darwin/amd64
nsq: nsqd v0.3.6-alpha (built w/go1.5); git revision: 1746cc6
The text was updated successfully, but these errors were encountered: