You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kvrocks.apache.org by "iushas (via GitHub)" <gi...@apache.org> on 2023/06/19 07:09:27 UTC
[GitHub] [incubator-kvrocks] iushas created a discussion: replication lag is to big
GitHub user iushas created a discussion: replication lag is to big
redis:
<img width="703" alt="image" src="https://github.com/apache/incubator-kvrocks/assets/7236171/b1ae2cee-7ed8-4b98-ad74-9c9b1318d428">
kvrocks:
<img width="665" alt="image" src="https://github.com/apache/incubator-kvrocks/assets/7236171/6f035e6c-c33f-49bb-a9bb-e19bf5e1534e">
use the same press test command， redis's master replication lag is always 0 or 1 ， kvrocks‘s lag is very big, why?
this can lead slave after master too much， how to resove!!
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] git-hulk added a comment to the discussion: replication lag is to big
Posted by "git-hulk (via GitHub)" <gi...@apache.org>.
GitHub user git-hulk added a comment to the discussion: replication lag is to big
The lag is totally different between Kvrocks and Redis. For the Redis, the lag means the replication seconds between the master and replica. But for the Kvrocks, it represents the write sequence gap. So I think you can relax the alert threshold value for the Kvrocks' lag like 1024 or others.
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216089
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] iushas added a comment to the discussion: replication lag is too big
Posted by "iushas (via GitHub)" <gi...@apache.org>.
GitHub user iushas added a comment to the discussion: replication lag is too big
then how we know kvrocks slave and master's offset diff , like redis ？
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216472
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] git-hulk added a comment to the discussion: replication lag is too big
Posted by "git-hulk (via GitHub)" <gi...@apache.org>.
GitHub user git-hulk added a comment to the discussion: replication lag is too big
For the Kvrocks, the lag is the indeed replication offset, but for the Redis is the last replication/interaction time. So as mentioned in the first comment, you should relax the alert threshold value for Kvrocks.
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216506
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] git-hulk added a comment to the discussion: replication lag is too big
Posted by "git-hulk (via GitHub)" <gi...@apache.org>.
GitHub user git-hulk added a comment to the discussion: replication lag is too big
Sure, the write sequence is equal to the number of KV that were written in RocksDB. For example, it will increase 1 if the command is `set a b`, and increase 2 if the command is `hset hash f1 v1` since it will write the metadata and subkey.
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216445
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] iushas added a comment to the discussion: replication lag is too big
Posted by "iushas (via GitHub)" <gi...@apache.org>.
GitHub user iushas added a comment to the discussion: replication lag is too big
sorry ，
did not understand. What's the write sequence gap mean， could you tell me more about it？
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216176
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] iushas edited a discussion: replication lag is too big
Posted by "iushas (via GitHub)" <gi...@apache.org>.
GitHub user iushas edited a discussion: replication lag is too big
redis:
<img width="703" alt="image" src="https://github.com/apache/incubator-kvrocks/assets/7236171/b1ae2cee-7ed8-4b98-ad74-9c9b1318d428">
kvrocks:
<img width="665" alt="image" src="https://github.com/apache/incubator-kvrocks/assets/7236171/6f035e6c-c33f-49bb-a9bb-e19bf5e1534e">
use the same press test command， redis's master replication lag is always 0 or 1 ， kvrocks‘s lag is very big, why?
this can lead slave after master too much， how to resove!!
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org
[GitHub] [incubator-kvrocks] iushas added a comment to the discussion: replication lag is too big
Posted by "iushas (via GitHub)" <gi...@apache.org>.
GitHub user iushas added a comment to the discussion: replication lag is too big
ok ，understand, thanks !
GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1504#discussioncomment-6216554
----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org