Vladislav Zolotarov
Vladislav Zolotarov
cc @tomer-sandler @harel-z @gcarmin
> Wait for 5.3 and 2023.1 that should change how latency is calculated, and then decide We need a solution for 2022.x, @amnonh. We can't wait for 2023.1. Wouldn't filtering...
@amnonh there must be a typo in your patch or something. I don't see how #2022 fixes this issue. Reopening
> @vladzcloudius Can you verify that the issue is solved with ScyllaDB > 2023.1 and setting the recording rule calculation to 20s? Why do we need to increase recording rules...
> @vladzcloudius It's decreasing. If it's lower than 20s, it's fine, but before 2023.1, it used to be 1m, and it is the root cause of the issue. > >...
> @vladzcloudius how to extract this info? The easiest way is to check the output of `perftune.py` and see which CPUs it binds NIC IRQs to. There are other ways...
@AdamStawarz Please, add a reference to a corresponding ZD ticket.
@amnonh Is it hard to implement?
> Sounds like something that needs to be done with a dns/service discovery Imagine a situation when a DNS resolves to a public IP (as expected) while scraping is done...