-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
producer: panic in popTransaction #171
Comments
definitely sounds like a bug of some sort. @chzyer can you confirm what version go-nsq you are using, and w/ what version of Go. Also, to clarify was this a panic you saw once, or is it recurring for you? |
The only thing i can think of is if a connection gets an unexpected |
Strange, never seen this before. @chzyer do you have more of the logs for the process that crashed so we can see the event in context? |
I meet this too. It throw error massage "not connected" before panic. |
@RobitYadda can you share logs that include the context of your error? |
My code like this: for{
//other process
go func() {
err = writer.Publish("events", msgBytes)
if err != nil {
glog.Errorf("%v", err)
}
}()
} Logs(some are logged nsq-client,others are logged by glog above):
|
I looked at @RobitYadda @chzyer I wrote a small program attempting to reproduce this issue with no luck. Are you able to repro with the above code? Are there any modifications you can make to make it repro? My logs:
|
The link return 404 |
@RobitYadda I accidentally linked to the edit page.. try now. |
For a minute I thought this might be a race with |
Hi, guys. I have meet a unexpected panic in producer, but I couldn't figure out how it happens.
Here is the panic log, and the version of
go-nsq
is newest.I check
(*Producer) popTransaction()
,t := w.transactions[0]
cause the crash, so I check all the functions which manipulatew.transactions
. Unfortunately, all the functions only use in(*Producer).router()
, which means there is not possible occurs the data races things.So, Is there any other possible ? Thanks.
The text was updated successfully, but these errors were encountered: