Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Async flash #781

Open
wants to merge 72 commits into
base: main
Choose a base branch
from
Open

Async flash #781

wants to merge 72 commits into from

Conversation

JohnSully
Copy link
Collaborator

No description provided.

JohnSully and others added 30 commits September 17, 2023 23:41
* Overload CPU reading metric

* fix

* fix
update insufficient replicas metrics to separate severity
* update overload-ignore-list to be use subnets as well

* get ip directly from conn

* add getIPV4 impl

* ntohl

* don't shift at the end of the loop

* update for more efficient impl and add ipv6 support

* array of arrays

* one combined array

* have to reassign output of sdscat

* include mask in operator<

* replace raw numbers with constants

* add log when we ignore client for loadshedding
…243)

* add overload-protect-tenacity to configure how many clients to evict

* need to divide tenacity config by 100 to get percentage
* TLS cname loadshedding ignore list
@keithchew
Copy link

Hi @JohnSully

I have started testing this branch with fastsync enabled, up to your latest commit:

f886fce

Just a few observations, please ignore if there are irrelevant as I understand this branch is still work in progress:

Transfer speed is very slow

On master, I see these in the logs:

7:71:M 06 Apr 2024 03:48:12.584 * Starting fast full sync with target: disk
7:59:M 06 Apr 2024 03:49:24.193 * Replication status: Transferred 105MB (0.01Gbit/s)
NOTICE: Detuning locks due to high load per core: 93.62%
7:59:M 06 Apr 2024 03:50:35.126 * Replication status: Transferred 129MB (0.00Gbit/s)
NOTICE: Detuning locks due to high load per core: 91.63%
...

With RDB, the size is 4GB and completes pretty quick, so likely something is not quite configured correctly on my instance.

Loading flag

Is it possible to set the loading flag after the replica flushes the data? For RDB, when the loading flag is set, the replica will reject commands during loading so the client can handle this condition, without the loading flag the client will think the incomplete data is correct and handles this case differently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants