Skip to content

[BUG] keydb gets extremely slow when master is not available #613

Open

Description

@cjabrantes

Hi all,

Describe the bug
Seems to be an issue with keydb when using --active-replica and --replicaof --multi-master.
When one instance goes down (and that also makes the dns to not resolve the fqdn) the remaining instance goes extremely slow:
time redis-cli -p 6379 ping
PONG
real 0m28.525s
user 0m0.007s
sys 0m0.006s

Does anyone have any idea of this situation?

version: keydb:x86_64_v6.0.9

If i set REPLICAOF NO ONE on the remaining instance it start to work fast again.

To reproduce

make that DNS is not aware of the FQDN present of REPLICAOF (in k8s scale down the sts)

Expected behavior

No slowness should be observed just because keydb can't resolve or dont have the master available

Thanks,

Activity

  1. changed the title [-][BUG][/-] [+][BUG] keydb gets extremely slow when master is not available[/+] on Mar 22, 2023
  2. artarik commented on Apr 17, 2024

    @artarik

    can you try use param multi-master-no-forward yes ?

  3. cjabrantes commented on May 20, 2024

    @cjabrantes
    Author

    hi @artarik,

    Sorry i didn't receive the notification for your updated and as the tickets have so much time i wasn't checking with regularity.
    I will test and let you know.

    Thanks!

  4. cjabrantes commented on May 20, 2024

    @cjabrantes
    Author

    hi @artarik,
    sadly i m not able to reproduce anymore :( with the as is config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions