2015-05-01 13:31 阅读 159


I am using the redigo library to try to subscribe to a Redis channel and then handle a published message. How do I handle the case where it errors out? Here's what I came up with. Is this a good way to do it? Is there a better way?

Note: this question is specific to redigo, but I think it applies to other places where reconnections need to happen.

package main

import (


func main() {
    for {
        c, err := redis.Dial("tcp", "localhost:6379")
        if err != nil {
            fmt.Println("error connecting to redis")
            time.Sleep(5 * time.Second)
        psc := redis.PubSubConn{c}
        for {
            switch v := psc.Receive().(type) {
            case redis.Message:
                fmt.Printf("%s: message: %s
", v.Channel, v.Data)
            case redis.Subscription:
                fmt.Printf("%s: %s %d
", v.Channel, v.Kind, v.Count)
            case error:
                fmt.Println("there was an error")
                time.Sleep(5 * time.Second)
                break ReceiveLoop

I just put it in the main() function for the example. It would really run in some goroutine.

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享

1条回答 默认 最新

  • 已采纳
    dpl3350 dpl3350 2015-05-01 19:29

    Yes, using a label and a loop is standard practice for reconnecting.

    The only thing you're missing is closing the connection.

                break ReceiveLoop

    For a little more resilience, you may want redis.DialTimeout so that a Dial call can't hang indefinitely.

    点赞 评论 复制链接分享