Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-73

Panic from cluster monitor closing channel during Stop

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 0.0.1
    • Affects Version/s: None
    • Component/s: Monitoring
    • None

      When i start it with ./bin/mongosqld -vvv, I get this panic after sampling is completed:

      panic: send on closed channel
      
      goroutine 36 [running]:
      github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer.func1(0xc420138240, 0xc420138120)
          /Users/wisdom/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:188 +0x92
      created by github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer
          /Users/wisdom/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:190 +0x12f```
      

      The panic is caused by this line: https://github.com/10gen/sqlproxy/blob/1ed515047a089fed7c64906948622743252eafeb/server/server.go#L103 though it's not clear why the driver bugs out because of that Close().

      I suspect it is a problem in the Go driver but haven't been able to pin it down.

            Assignee:
            craig.wilson@mongodb.com Craig Wilson
            Reporter:
            adinoyi.omuya@mongodb.com Adinoyi Omuya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: