Channels
  • g

    Guy E Matz

    11 months ago
    Thank you!
    10.27.141.59:6379> info
    # Server
    redis_version:5.0.9
  • zwass

    zwass

    11 months ago
    Is this a standard Redis deployment? Or a managed one? What do you get for the rest of that
    info
    command?
    If you are self managing Redis, can you share the contents of your
    redis.conf
    (with any password redacted)?
  • j

    Jason

    11 months ago
    it's GCP managed Redis I believe - right @Guy E Matz??
  • g

    Guy E Matz

    11 months ago
    Correct
  • zwass

    zwass

    11 months ago
    Ah, it seems GCP disables the
    CLUSTER
    command (https://cloud.google.com/memorystore/docs/redis/product-constraints#blocked_redis_commands) which means we see a different error than what we expect when we try that command with clustering not in use.
  • j

    Jason

    11 months ago
    Should we file an issue? And what would you suggest the workaround be? Should we spin up a non-managed redis instance until this is resolved?
  • zwass

    zwass

    11 months ago
    Quickest solution would be spinning up a non-managed redis instance. We'll be able to push a fix for this in the next release.
    Or reverting to Fleet 3.13.0
    Or you can build binaries/Docker containers yourself after I merge the fix.
  • j

    Jason

    11 months ago
    got it. Very helpful - thanks!
  • zwass

    zwass

    11 months ago
  • g

    Guy E Matz

    11 months ago
    Thanks again. I migrated the DB when I upgraded to 4.0 . . . do I need to rebuild the DB after reverting to 3.13?
  • zwass

    zwass

    11 months ago
    Yes, restore from a backup or rebuild the DB.
  • g

    Guy E Matz

    11 months ago
    Thanks!
  • f

    Flngen Flugen

    7 months ago
    I'm having this issue on kubernetes with fleetdm v4 image. Is there a new docker image that fixed this issue?