Type-safe Redis client for Golang

Overview

Redis client for Golang

Build Status PkgGoDev Documentation Chat

❤️ Uptrace.dev - distributed traces, logs, and errors in one place

Ecosystem

Features

Installation

go-redis supports 2 last Go versions and requires a Go version with modules support. So make sure to initialize a Go module:

go mod init github.com/my/repo

And then install go-redis/v8 (note v8 in the import; omitting it is a popular mistake):

go get github.com/go-redis/redis/v8

Quickstart

import (
    "context"
    "github.com/go-redis/redis/v8"
)

var ctx = context.Background()

func ExampleClient() {
    rdb := redis.NewClient(&redis.Options{
        Addr:     "localhost:6379",
        Password: "", // no password set
        DB:       0,  // use default DB
    })

    err := rdb.Set(ctx, "key", "value", 0).Err()
    if err != nil {
        panic(err)
    }

    val, err := rdb.Get(ctx, "key").Result()
    if err != nil {
        panic(err)
    }
    fmt.Println("key", val)

    val2, err := rdb.Get(ctx, "key2").Result()
    if err == redis.Nil {
        fmt.Println("key2 does not exist")
    } else if err != nil {
        panic(err)
    } else {
        fmt.Println("key2", val2)
    }
    // Output: key value
    // key2 does not exist
}

Look and feel

Some corner cases:

// SET key value EX 10 NX
set, err := rdb.SetNX(ctx, "key", "value", 10*time.Second).Result()

// SET key value keepttl NX
set, err := rdb.SetNX(ctx, "key", "value", redis.KeepTTL).Result()

// SORT list LIMIT 0 2 ASC
vals, err := rdb.Sort(ctx, "list", &redis.Sort{Offset: 0, Count: 2, Order: "ASC"}).Result()

// ZRANGEBYSCORE zset -inf +inf WITHSCORES LIMIT 0 2
vals, err := rdb.ZRangeByScoreWithScores(ctx, "zset", &redis.ZRangeBy{
    Min: "-inf",
    Max: "+inf",
    Offset: 0,
    Count: 2,
}).Result()

// ZINTERSTORE out 2 zset1 zset2 WEIGHTS 2 3 AGGREGATE SUM
vals, err := rdb.ZInterStore(ctx, "out", &redis.ZStore{
    Keys: []string{"zset1", "zset2"},
    Weights: []int64{2, 3}
}).Result()

// EVAL "return {KEYS[1],ARGV[1]}" 1 "key" "hello"
vals, err := rdb.Eval(ctx, "return {KEYS[1],ARGV[1]}", []string{"key"}, "hello").Result()

// custom command
res, err := rdb.Do(ctx, "set", "key", "value").Result()

Run the test

go-redis will start a redis-server and run the test cases.

The paths of redis-server bin file and redis config file are definded in main_test.go:

var (
	redisServerBin, _  = filepath.Abs(filepath.Join("testdata", "redis", "src", "redis-server"))
	redisServerConf, _ = filepath.Abs(filepath.Join("testdata", "redis", "redis.conf"))
)

For local testing, you can change the variables to refer to your local files, or create a soft link to the corresponding folder for redis-server and copy the config file to testdata/redis/:

ln -s /usr/bin/redis-server ./go-redis/testdata/redis/src
cp ./go-redis/testdata/redis.conf ./go-redis/testdata/redis/

Lastly, run:

go test

See also

Comments
  • undefined: otel.Meter or cannot find package

    undefined: otel.Meter or cannot find package "go.opentelemetry.io/otel/api/trace"

    To fix cannot find package "go.opentelemetry.io/otel/api/trace" or undefined: otel.Meter:

    1. Make sure to initialize a Go module: go mod init github.com/my/repo

    2. Make sure to use correct import path with v8 in the end: go get github.com/go-redis/redis/v8

    For example:

    mkdir /tmp/redis-test
    cd /tmp/redis-test
    go mod init redis-test
    go get github.com/go-redis/redis/v8
    

    The root cause

    The error is not caused by OpenTelemetry. OpenTelemetry is just the first module Go tries to install. And the error will not go away until you start using Go modules properly.

    The presence of $GOROOT or $GOPATH in error messages indicates that you are NOT using Go modules.

    opened by vmihailenco 33
  • V8 performance degradation ~20%

    V8 performance degradation ~20%

    @monkey92t

    Hi, thank you for your tests. I ran your tests in our environment, and saw similar comparative results. However, when I slightly modified the tests to reflect more accurately of our use case (and how Go HTTP spawn goroutine for each request), all the sudden the performance is degraded for V8. This is especially evident with 100+ concurrency.

    2 changes that were made:

    1. instead of pre-spawn Go routine and run fixed number of Get/Set in a for loop (this is retained using get2/set2), it runs through fixed number of requests and spawn a Go routine (only up to currency) to process them.
    2. each request will generate a random key so the load is spread across the Redis cluster.

    Both V7/V8 saw a decrease in throughput comparing using pre-spawn Go routines vs a Go routine per request. However, decrease for V7 is very small as expected, but V8 is quite dramatic.

    go-redis version: v7.4.0 and v8.6.0

    redis-cluster (version 5.0.7): master: 84 instances slave: 84 instances

    This is the RedisCluster test result: https://github.com/go-redis/redis/files/6158805/Results.pdf

    This is the test program: https://github.com/go-redis/redis/files/6158824/perftest.go.gz

    opened by jfjm2018 29
  • high memory usage + solution

    high memory usage + solution

    Hi,

    I noticed that the memory usage was very high in my project. I did a memory profiling with inuse_space, and 90% of my memory is used by go-redis in WriteBuffer. If I understand correctly, each connection in the pool has its own WriteBuffer.

    My projects runs 80 goroutines (on 8 CPUs) and each goroutine SET Redis keys. My Redis keys are large: several MB. (less than 100 MB) So, it's very easy to understand why the memory usage is very high.

    I think I have a solution, but it requires changes in go-redis internals. We could use a global sync.Pool of WriteBuffer instead.

    WDYT ?

    opened by pierrre 24
  • Constantly Reestablishing Connections in Cluster Mode

    Constantly Reestablishing Connections in Cluster Mode

    Expected Behavior

    Creating a cluster client using pretty much default settings should not overwhelm Redis with constant barrage of new connections.

    redis.NewClusterClient(&redis.ClusterOptions{
        Addrs: []string{redisAddr},
        TLSConfig: &tls.Config{},
    })
    

    Current Behavior

    Occasionally, at times completely unrelated to system load/traffic, we are seeing connections being constantly re-established to one of the cluster nodes in our Redis cluster. We are using ElastiCache Redis in cluster mode with TLS enabled, and there seems to be no trigger we can find for this behavior. We also do not see any relevant logs in our service's systemd output in journalctl, other than

    redis_writer:85 {}        Error with write attempt: context deadline exceeded
    

    which seems more like a symptom of an overloaded Redis cluster node rather than a cause.

    When this issue happens, running CLIENT LIST on the affected Redis node shows age=0 or age=1 for all connections every time, which reinforces that connections are being dropped constantly for some reason. New connections plummet on other shards in the Redis cluster, and are all concentrated on one.

    New Connections (Cloudwatch)

    NewConnections

    Current Connections (Cloudwatch)

    CurrConnections

    In the example Cloudwatch graphs above we can also see that the issue can move between Redis cluster shards. As you can see, we're currently running with a 4-shard cluster, where each shard has 1 replica.

    Restarting our service does not address this problem, and to address it we basically need to do a hard reset (completely stop the clients for a while, then start them up again).

    We've reached out to AWS support and they have found no issues with our ElastiCache Redis cluster on their end. Additionally, there are no ElastiCache events happening at the time this issue is triggered.

    Possible Solution

    In this issue I'm mainly hoping to get insight into how I could better troubleshoot this issue and/or if there are additional client options we can use to try and mitigate this worst case scenario (i.e. rate limiting the creation of new connections in the cluster client) in absence of a root-cause fix.

    My main questions are:

    1. Is there a way for me to gather more data that would be helpful for the Redis/go-redis experts here?
    2. Is there a way for us to rate-limit the creation of new connections in the ClusterClient to keep things from getting too out of control if this does continue to occur?
    3. Has anyone else encountered a similar issue with Cluster mode, whether or not it was with ElastiCache Redis?

    Steps to Reproduce

    The description of our environment/service implementation below, as well as the snippet of our NewClusterClient call at the beginning of this issue, provide a fairly complete summary of how we're using both go-redis and ElastiCache Redis. We've not been able to consistently trigger this issue since it often happens when we're not load testing, and are mainly looking for answers for some of our questions above.

    Context (Environment)

    We're running a service that has a simple algorithm for claiming work from a Redis set, doing something with it, and then cleaning it up from Redis. In a nutshell, the algorithm is as follows:

    • SRANDMEMBER pending 10 - grab up to 10 random items from the pool of available work
    • ZADD in_progress <current_timestamp> <grabbed_item> for each of our items we got in the previous step
    • Any work items we weren't able to ZADD have been claimed by some other instance of the service, skip them
    • Once we're done with a work item, SREM pending <grabbed_item>
    • Periodically ZREMRANGEBYSCORE in_progress -inf <5_seconds_ago> so that claimed items aren't claimed forever

    Currently we run this algorithm on 6 EC2 instances, each running one service. Since each instance has 4 CPU cores, go-redis is calculating a max connection pool size of 20 for our ClusterClient. Each service has 20 goroutines performing this algorithm, and each goroutine sleeps 10ms between each invocation of the algorithm.

    At a steady state with no load on the system (just a handful of heartbeat jobs being added to pending every minute) we see a maximum of ~8% EngineCPUUtilization on each Redis shard, and 1-5 new connections/minute. Overall, pretty relaxed. When this issue has triggered recently, it's happened from this steady state, not during load tests.

    Our service is running on EC2 instances running Ubuntu 18.04 (Bionic), and we have tried using github.com/go-redis/redis/v8 v8.0.0 and github.com/go-redis/redis/v8 v8.11.2 - both have run into this issue.

    As mentioned earlier, we're currently running with a 4-shard ElastiCache Redis cluster with TLS enabled, where each shard has 1 replica.

    Detailed Description

    N/A

    Possible Implementation

    N/A

    opened by ianjhoffman 22
  • Add redis.Scan() to scan results from redis maps into structs.

    Add redis.Scan() to scan results from redis maps into structs.

    The package uses reflection to decode default types (int, string etc.) from Redis map results (key-value pair sequences) into struct fields where the fields are matched to Redis keys by tags.

    Similar to how encoding/json allows custom decoders usingUnmarshalJSON(), the package supports decoding of arbitrary types into struct fields by defining a Decode(string) errorfunction on types.

    The field/type spec of every struct that's passed to Scan() is cached in the package so that subsequent scans avoid iteration and reflection of the struct's fields.

    Issue: https://github.com/go-redis/redis/issues/1603

    opened by knadh 20
  • hscan adds support for i386 platform

    hscan adds support for i386 platform

    set: GOARCH=386

    redis 127.0.0.1:6379>>set a 100
    redis 127.0.0.1:6379>>set b 123456789123456789
    
    type Demo struct {
        A int8 `redis:"a"`
        B int64 `redis:"b"`
    }
    
    client := redis.NewClient(&Options{
            Network:      "tcp",
            Addr:         "127.0.0.1:6379",
    })  
    ctx := context.Background()
    d := &Demo{}
    err := client.MGet(ctx, "a", "b").Scan(d)
    t.Log(d, err)
    

    it should run normally on the i386 platform, and there should not be such an error: strconv.ParseInt: parsing "123456789123456789": value out of range

    opened by monkey92t 18
  • Add Limiter interface

    Add Limiter interface

    This is an alternative to https://github.com/go-redis/redis/pull/874. Basically it defines rate limiter interface which allows to implement different limiting strategies in separate packages.

    @xianglinghui what do you think? Is provided API enough to cover your needs? I am aware that code like https://github.com/go-redis/redis/blob/master/ring.go#L618-L621 requires some work in go-redis, but other than that it seems to be enough.

    opened by vmihailenco 17
  • connection pool timeout

    connection pool timeout

    I am using Redis as a caching layer for long running web services. I initialize the connection like so:

    var (
        Queues  *redis.Client
        Tracker *redis.Client
    )
    
    func Connect(url string) {
        // cut away redis://
        url = url[8:]
    
        // connect to db #0
        Queues = redis.NewClient(&redis.Options{
            Addr:     url,
            Password: "",
            DB:       0,
        })
    
        _, err := Queues.Ping().Result()
        if err != nil {
            panic(err)
        }
    
        // connect to db #1
        Tracker = redis.NewClient(&redis.Options{
            Addr:     url,
            Password: "",
            DB:       1,
        })
    
        _, err = Tracker.Ping().Result()
        if err != nil {
            panic(err)
        }
    }
    

    Abeit in an upcoming patch (sysadmin is deploying a Redis cluster) it will be like so:

    var (
        Cluster *redis.ClusterClient
    )
    
    func ConnectCluster(cluster, password string) {
        addresses := strings.Split(cluster, ",")
        Cluster = redis.NewClusterClient(&redis.ClusterOptions{
            Addrs: addresses,
            // Password: password,
        })
    
        _, err := Cluster.Ping().Result()
        if err != nil {
            panic(err)
        }
    }
    

    The above code gets run once when service boots up in main.go and the *redis.ClusterClient is being used for the lifetime of the process.

    I realize there is an iherent problem with this approach, which is manifesting itself in connections timing out after a few days, and crashing the application: redis: connection pool timeout See logs here

    Please advise, what would be a proper approach to use go-redis in this situation?

    opened by Netherdrake 16
  • dial tcp: i/o timeout

    dial tcp: i/o timeout

    I am using go-redis version v6.14.2. I have my application running in an AWS cluster behind loadbalancer. All redis requests failed in one of the nodes in the cluster. Rest of the nodes were working as expected. Application started working properly after a restart. We are using ElastiCache. Can you please help me with identifying the issue ?? If it is previously known issue and is solved in latest version, can you point me to that link ??

    The error was "dial tcp: i/o timeout".

    Below is my cluster configuration excluding redis host address and password:

    • ReadOnly : true
    • RouteByLatency : true
    • RouteRandomly : true
    • DialTimeout : 300ms
    • ReadTimeout : 30s
    • Write Timeout : 30s
    • PoolSize : 12000
    • PoolTimeout : 32
    • IdleTimeout : 120s
    • IdleCheckFrequency : 1s
    import (
    goRedisClient "github.com/go-redis/redis"
    )
    
    func GetRedisClient() *goRedisClient.ClusterClient {
    clusterClientOnce.Do(func() {
    redisClusterClient = goRedisClient.NewClusterClient(
    &goRedisClient.ClusterOptions{
    Addrs: viper.GetStringSlice("redis.hosts"),
    ReadOnly: true,
    RouteByLatency: true,
    RouteRandomly: true,
    Password: viper.GetString("redis.password"),
    
    			DialTimeout:  viper.GetDuration("redis.dial_timeout"),
    			ReadTimeout:  viper.GetDuration("redis.read_timeout"),
    			WriteTimeout: viper.GetDuration("redis.write_timeout"),
    
    			PoolSize:           viper.GetInt("redis.max_active_connections"),
    			PoolTimeout:        viper.GetDuration("redis.pool_timeout"),
    			IdleTimeout:        viper.GetDuration("redis.idle_connection_timeout"),
    			IdleCheckFrequency: viper.GetDuration("redis.idle_check_frequency"),
    		},
    	)
    
    	if err := redisClusterClient.Ping().Err(); err != nil {
    		log.WithError(err).Error(errorCreatingRedisClusterClient)
    	}
    })
    return redisClusterClient
    }
    

    As suggested in comments,https://github.com/go-redis/redis/issues/1194, I wrote the following snippet to dial and test nodes health for each slot. There were no errors. As mentioned, its happening randomly in one of the clients.Not always. It happened again after 3-4 months. And it is always fixed after a restart.

    func CheckRedisSlotConnection(testCase string) {
    	fmt.Println(viper.GetStringSlice("redis.hosts"))
    	fmt.Println("Checking testcase " + testCase)
    	client := redis.GetRedisClient()
    	slots := client.ClusterSlots().Val()
    	addresses := []string{}
    	for _, slot := range slots {
    		for _, node := range slot.Nodes {
    			addresses = append(addresses, node.Addr)
    		}
    	}
    	fmt.Println("Received " + strconv.Itoa(len(addresses)) + " Slots")
    	for _, address := range addresses {
    		fmt.Println("Testing address " + address)
    		conn, err := net.DialTimeout("tcp", address, 500*time.Millisecond)
    		if err != nil {
    			fmt.Println("Error dialing to address " + address + " Error " + err.Error())
    			continue
    		}
    		fmt.Println("Successfully dialled to address " + address)
    		err = conn.Close()
    		if err != nil {
    			fmt.Println("Error closing connection " + err.Error())
    			continue
    		}
    	}
    }
    
    opened by srinidhis94 15
  • Attempt to cleanup cluster logic.

    Attempt to cleanup cluster logic.

    @dim I tried to refactor code a bit to learn more about Redis cluster. Changes:

    • NewClusterClient does not return error any more, because NewClient does not too. I personally think that app can't do anything useful except exiting when NewClusterClient returns an error. So panic should be a good alternative.
    • Now ClusterClient.process tries next available replica before falling back to the randomClient. I am not sure that this change is correct, but I hope so :)
    • randomClient is completely rewritten so it does not require allocating seen map[string]struct{}{} on every request. It also checks that node is online before returning.
    opened by vmihailenco 15
  • How to implement periodic refresh topology

    How to implement periodic refresh topology

    My redis cluster is on top of kubernetes, so sometimes i may move the entire cluster to another set of nodes and they all change ip address. So my go-redis client needs to refresh the topology from time to time. I am wondering is there a config to do that? Or do i need to send some cluster-nodes command from time to time?

    opened by smartnews-weitao 14
  • fix(iterator): remove unnecessary mutex

    fix(iterator): remove unnecessary mutex

    The mutex was removed in v9 in #2184 as the iterator cannot be used concurrently so I think we should also drop it in v8. Assuming v8 is still supported as it is mentioned in the installation section of the readme file

    opened by v3s1e 0
  • how to scan time.Time?

    how to scan time.Time?

    cannot scan redis.result 2022-11-25 16:05:00.5789249 +0900 JST m=+0.000944801 into struct field Account.CreatedAt of type time.Time, error-redis.Scan(unsupported time.Time)

    scan without time.Time support makes nonsense. bro time matters, especially for something like a database.

    opened by ntswamp 0
  • startSentinel in main_test.go fails

    startSentinel in main_test.go fails

    I ran unit testcases followed the instruction specified here:https://github.com/go-redis/redis#run-the-test. but sentinel cloud not start successfully. after searching issue in https://github.com/redis, I found a similar issue:https://github.com/redis/redis/issues/1463, then I changed the line 339 in main_test.go from:

    process, err := execCmd(redisServerBin, sentinelConf, "--sentinel", "--port", port, "--dir", dir)
    

    into:

    process, err := execCmd(redisServerBin, sentinelConf, "--port", port, "--dir", dir, "--sentinel")
    

    and problem solved. is it just me or is there a common issue here?

    Expected Behavior

    sentinel should start successfully

    Current Behavior

    sentinel start fails with error:

    *** FATAL CONFIG FILE ERROR (Redis 7.0.5) ***
    Reading the configuration file, at line 27
    >>> 'sentinel "--port" "9126"'
    Unrecognized sentinel configuration statement.
    

    Possible Solution

    as above

    Steps to Reproduce

    1. clone master
    2. go test

    Context (Environment)

    Redis 7.0.5

    opened by boatrainlsz 0
  • Blocking XGroupCreateMkStream does not interrupt on context cancellation

    Blocking XGroupCreateMkStream does not interrupt on context cancellation

    When XGroupCreateMkStream is called in blocking mode (Block = 0), call does not get interrupted by cancelling context.

    Expected Behavior

    Blocking function interrupts when context is cancelled

    Current Behavior

    Function continues to block after context cancellation

    Possible Solution

    Unsure yet

    Steps to Reproduce

    package main
    
    import (
    	"context"
    	"fmt"
    	"sync"
    	"time"
    
    	"github.com/go-redis/redis/v9"
    	"github.com/google/uuid"
    )
    
    func main() {
    	rdb := redis.NewUniversalClient(&redis.UniversalOptions{
    		Addrs:    []string{"localhost:6379"},
    		Password: "", // no password set
    		DB:       0,  // use default DB
    	})
    
    	defer rdb.Close()
    
    	ctx, cancelFn := context.WithCancel(context.Background())
    
    	go func() {
    		for idx := 0; idx < 5; idx++ {
    			fmt.Printf("Waiting %v...\n", idx)
    			time.Sleep(time.Second)
    		}
    		cancelFn()
    		fmt.Printf("Cancelled context and now expect blocking XGroupCreateMkStream to be interrupted...\n")
    	}()
    
    	name := "blag"
    	streamName := name
    	groupName := name + "-blah"
    
    	_, err := rdb.XGroupCreateMkStream(ctx, streamName, groupName, "0").Result()
    	fmt.Printf("%v\n", err)
    
    	var wg sync.WaitGroup
    
    	wg.Add(1)
    	go func() {
    		defer wg.Done()
    		objs, err := rdb.XReadGroup(ctx, &redis.XReadGroupArgs{
    			Group:    groupName,
    			Consumer: uuid.NewString(),
    			Streams:  []string{streamName, ">"},
    			Count:    100,
    			Block:    0,
    		}).Result()
    		fmt.Printf("%v, %v\n", err, objs)
    	}()
    
    	wg.Wait()
    	fmt.Printf("Done.\n")
    }
    
    

    Context (Environment)

    I have two goroutines concurrently performing XREADGROUP and XADD in blocking mode. XADD is triggered by external events and is not guaranteed to add items to the stream at any particular cadence or pattern. Shutting down reading goroutine is not possible due to the blocking call that does not get interrupted by context concellation.

    Detailed Description

    Blocking calls should interrupt when context is cancelled and connection closed.

    Possible Implementation

    N/A

    opened by jgirtakovskis 0
  • On MOVED response and on cluster refresh, the lib will not revalidate if the hostname still points to the same IP address

    On MOVED response and on cluster refresh, the lib will not revalidate if the hostname still points to the same IP address

    Expected Behavior

    On a MOVED response from Redis or when refreshing the cluster nodes, the library should validate that the hostname associated to the MOVED response or the one coming from CLUSTER SLOTS still points to the same IP.

    Current Behavior

    With maxRedirects above 0, the library will reissue the command on the node instructed in the MOVED reply. This works in most cases but does not account for the fact that the DNS returned by the response might not point to the same IP anymore, rendering the redirection handling useless.

    The same behavior is present on cluster refresh.

    Possible Solution

    When handling a MOVED response, the library should assert that the DNS resolves to the same IP and mark the node as failing or force a synchronous refresh.

    Steps to Reproduce

    Hard to reproduce manually but I've included a lot information in the next sections.

    Context (Environment)

    This is happening using an AWS Elasticache cluster during an engine update from 6.0 -> 6.2. It's a cluster with 1 shard and 2 replicas. While technically MOVED responses should not happen in a single shard cluster, AWS uses it during the cluster update. We have opened a support case to get more information on the update process, I'll report back if there is anything interesting on this side.

    The library version used is v8.11.5.

    Detailed Description

    I've spent a bunch of times trying to get to the bottom of this issue since we're trying to have an error-less engine update in our production environment. I've ended up using the mode readOnly: false because it's the mode that was causing the least amount of errors. I'm not exactly sure of the cause of the difference (might be related to this issue or not).

    Update behavior from the DNS side

    I've traced every second the result of the various DNS queries associated to the Elasticache cluster during an update (the configuration endpoint and node dedicated endpoints). Here are the results. In this case, initially, the master node was test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com. During the update, it's hard to say because AWS seem to be using resharding inside the cluster and there are multiples instances reporting to be the master at the same time. After the update process, test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com is the new final master.

    As you can see below, the old nodes being decommissionned are still valid during the update.

    Initial 
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.9.206
    test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.9.206
    test-jbeaudet-0001-002.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    test-jbeaudet-0001-003.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    
    2022-10-31T15:11:38.722955
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.9.206
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    test-jbeaudet-0001-002.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    test-jbeaudet-0001-003.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    
    2022-10-31T15:15:46.533745
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.9.206
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    test-jbeaudet-0001-002.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    test-jbeaudet-0001-003.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    
    2022-10-31T15:16:47.835160
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.9.206
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.6.107
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.0.17
    test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    test-jbeaudet-0001-002.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    test-jbeaudet-0001-003.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    
    2022-10-31T15:26:12.539041
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    clustercfg.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.10.86
    test-jbeaudet-0001-002.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.7.90
    test-jbeaudet-0001-003.test-jbeaudet.9chuso.usw2.cache.amazonaws.com/172.30.1.66
    

    Behavior in the library

    During the update, our application issuing GET commands on the master only, started receiving MOVED 4559 test-jbeaudet-0001-001.test-jbeaudet.9chuso.usw2.cache.amazonaws.com:6379. This response is handled here and uses the hostname to fetch the node here. However, like we can see in the previous section, that DNS points to a new IP address! But since the code does not handle that case, it reissues the command to the same node, getting a new MOVED response and does this until the maxRedirects count has been reached.

    The same behavior happens when reloading the cluster state here, nothing validates that the DNS endpoint has changed so you're stuck with connections pointing to the old node of the cluster being decommissioned.

    I wish I could propose a solution but I'm not super familiar with the intricacies of the library.

    Thanks for looking into it!

    opened by jbeaudetupgrade 0
  • v9: `rediscensus.TracingHook` doesn't implement `redis.Hook`

    v9: `rediscensus.TracingHook` doesn't implement `redis.Hook`

    package main
    
    import (
    	"github.com/go-redis/redis/extra/rediscensus/v9"
    	"github.com/go-redis/redis/v9"
    )
    
    func main() {
    	client := redis.Client{}
    	client.AddHook(rediscensus.TracingHook{})
    }
    

    Expected Behavior

    rediscensus.TracingHook should implement redis.Hook.

    Current Behavior

    It does not.

    # github.com/go-redis/redis/extra/rediscensus/v9
    ../gopath3627430044/pkg/mod/github.com/go-redis/redis/extra/rediscensus/[email protected]/rediscensus.go:14:20: cannot use (*TracingHook)(nil) (value of type *TracingHook) as type redis.Hook in variable declaration:
    	*TracingHook does not implement redis.Hook (missing DialHook method)
    
    Go build failed.
    

    Steps to Reproduce

    https://go.dev/play/p/pbe3qBaLVqj

    opened by dcormier 0
Releases(v9.0.0-rc.2)
  • v9.0.0-rc.2(Nov 26, 2022)

  • v9.0.0-rc.1(Oct 14, 2022)

  • v9.0.0-beta.3(Oct 6, 2022)

  • v9.0.0-beta.2(Jul 28, 2022)

  • v9.0.0-beta.1(Jun 4, 2022)

  • v8.11.5(Mar 17, 2022)

  • v8.11.4(Oct 4, 2021)

  • v8.11.2(Aug 6, 2021)

    Important changes:

    Revert #1824, because it will have a significant impact on the connection pool(#1849) We will re-add this feature in v9.

    Users who have already used v8.11.1, need to upgrade immediately.

    Source code(tar.gz)
    Source code(zip)
  • v8.11.1(Jul 29, 2021)

    Enhancement:

    • DBSize,ScriptLoad,ScriptFlush and ScriptExists should use hook. (#1811)
    • Added FIFO option to connection pool, set option Options.PoolFIFO to true. (#1820)
    • The connection is checked before use, it will increase the CPU time by 5-10% (#1824)
    • Check Failing() before serving random node. (#1825)

    Command:

    • RPOP command supports Count option (redis-server >= 6.2)
    • New cmd: GeoSearch, GeoSearchStore (redis-server >= 6.2)

    Thanks: @ktaekwon000 @hidu @AnatolyRugalev

    Source code(tar.gz)
    Source code(zip)
  • v7.4.1(Jul 16, 2021)

  • v8.11.0(Jun 30, 2021)

    Change

    Remove OpenTelemetry metrics, Linked #1534 #1805

    New Command

    1. XAutoClaim
    2. ZRangeStore
    3. ZUnion

    Command More Options

    1. XAdd: NoMkStream+MinID+Limit
    2. XTrim: MinID+Limit
    3. XGroup: CreateConsumer
    4. ZAdd: GT+LT
    5. ZRange: ByScore+ByLex+Rev+Limit

    New API

    1. XAutoClaim(ctx context.Context, a *XAutoClaimArgs) *XAutoClaimCmd
    2. XAutoClaimJustID(ctx context.Context, a *XAutoClaimArgs) *XAutoClaimJustIDCmd
    3. ZRangeStore(ctx context.Context, dst string, z ZRangeArgs) *IntCmd
    4. ZAddArgs(ctx context.Context, key string, args ZAddArgs) *IntCmd
    5. ZAddArgsIncr(ctx context.Context, key string, args ZAddArgs) *FloatCmd
    6. ZRangeArgs(ctx context.Context, z ZRangeArgs) *StringSliceCmd
    7. ZRangeArgsWithScores(ctx context.Context, z ZRangeArgs) *ZSliceCmd
    8. ZUnion(ctx context.Context, store ZStore) *StringSliceCmd
    9. ZUnionWithScores(ctx context.Context, store ZStore) *ZSliceCmd

    Mark deprecated(remove in v9)

    1. ZAddCh
    2. ZIncr
    3. ZAddNXCh
    4. ZAddXXCh
    5. ZIncrNX
    6. ZIncrXX
    7. XTrim
    8. XTrimApprox
    9. XAddArgs.MaxLenApprox

    Remarks

    There is a bug in the xtrim/xadd limit option (https://github.com/redis/redis/issues/9046)

    Source code(tar.gz)
    Source code(zip)
  • v8.10.0(Jun 3, 2021)

Golang client for redislabs' ReJSON module with support for multilple redis clients (redigo, go-redis)

Go-ReJSON - a golang client for ReJSON (a JSON data type for Redis) Go-ReJSON is a Go client for ReJSON Redis Module. ReJSON is a Redis module that im

Nitish Malhotra 291 Nov 17, 2022
Redis client Mock Provide mock test for redis query

Redis client Mock Provide mock test for redis query, Compatible with github.com/go-redis/redis/v8 Install Confirm that you are using redis.Client the

null 149 Nov 11, 2022
GoBigdis is a persistent database that implements the Redis server protocol. Any Redis client can interface with it and start to use it right away.

GoBigdis GoBigdis is a persistent database that implements the Redis server protocol. Any Redis client can interface with it and start to use it right

Riccardo 5 Apr 27, 2022
Bxd redis benchmark - Redis benchmark tool for golang

使用 redis benchmark 工具, 测试 10 20 50 100 200 1k 5k 字节 value 大小,redis get set 性能。 r

bingxindan 0 Jan 22, 2022
redis client implement by golang, inspired by jedis.

godis redis client implement by golang, refers to jedis. this library implements most of redis command, include normal redis command, cluster command,

piaohao 107 Nov 18, 2022
Redis client for Golang

Redis client for Golang To ask questions, join Discord or use Discussions. Newsl

null 0 Dec 23, 2021
Redis client for Golang

Redis client for Golang Discussions. Newsletter to get latest updates. Documentation Reference Examples RealWorld example app Other projects you may l

null 0 Dec 30, 2021
Go client for Redis

Redigo Redigo is a Go client for the Redis database. Features A Print-like API with support for all Redis commands. Pipelining, including pipelined tr

null 9.3k Nov 27, 2022
Go Redis Client

xredis Built on top of github.com/garyburd/redigo with the idea to simplify creating a Redis client, provide type safe calls and encapsulate the low l

Raed Shomali 19 Sep 26, 2022
godis - an old Redis client for Go

godis Implements a few database clients for Redis. There is a stable client and an experimental client, redis and exp, respectively. To use any of the

Simon Zimmermann 86 Apr 16, 2022
Google Go Client and Connectors for Redis

Go-Redis Go Clients and Connectors for Redis. The initial release provides the interface and implementation supporting the (~) full set of current Red

Joubin Houshyar 442 Oct 25, 2022
Redis client library for Go

go-redis go-redis is a Redis client library for the Go programming language. It's built on the skeleton of gomemcache. It is safe to use by multiple g

Alexandre Fiori 45 Nov 8, 2022
Redisx: a library of Go utilities built on the redigo redis client library

redisx redisx is a library of Go utilities built on the redigo redis client libr

null 1 Dec 24, 2021
A Golang implemented Redis Server and Cluster.

Godis is a golang implementation of Redis Server, which intents to provide an example of writing a high concurrent middleware using golang.

finley 2.4k Nov 26, 2022
A golang tool to view Redis data in terminal

Redis Viewer A tool to view Redis data in terminal. Usage: KeyBoard Description ctrl+c exit redis viewer ↑ previous key ↓ next key ← previous page → n

SaltFish 80 Nov 13, 2022
High-performance framework for building redis-protocol compatible TCP servers/services

Redeo The high-performance Swiss Army Knife for building redis-protocol compatible servers/services. Parts This repository is organised into multiple

Black Square Media 419 Nov 9, 2022
Simple key-value store abstraction and implementations for Go (Redis, Consul, etcd, bbolt, BadgerDB, LevelDB, Memcached, DynamoDB, S3, PostgreSQL, MongoDB, CockroachDB and many more)

gokv Simple key-value store abstraction and implementations for Go Contents Features Simple interface Implementations Value types Marshal formats Road

Philipp Gillé 490 Nov 21, 2022
Redis Sorted Sets Benchmark

redis-zbench-go Redis Sorted Sets Benchmark Overview This repo contains code to trigger load ( ZADD ) or query (ZRANGEBYLEX key min max) benchmarks, w

filipe oliveira 3 May 18, 2021
Use Redis' MONITOR to draw things in a terminal

Redis Top Redistop uses MONITOR to watch Redis commands and shows per command and per host statistics. Because MONITOR streams back all commands, its

Factory 31 Aug 30, 2022