Israel Fruchter comments

Results 1079 comments of


                                            Israel Fruchter

fix(full scan thread): Added missing fetch-next-page to fetch_result_pages

> @fruch, It looks like a bug in the code. But I'm guessing that this was deleted because the scan can be too big. And we are just getting command...

fix(full scan thread): Added missing fetch-next-page to fetch_result_pages

> > > @fruch, It looks like a bug in the code. But I'm guessing that this was deleted because the scan can be too big. And we are just...

fix(full scan thread): Added missing fetch-next-page to fetch_result_pages

> Testing: > [10gb-3h](https://jenkins.scylladb.com/job/scylla-staging/job/yarongilor/job/byo-longevity-test-yg/39/) > passed ok with output like: > ``` > < t:2024-10-27 18:09:05,695 f:scan_operation_thread.py l:100 c:FullScanOperation p:INFO > FullscanOperationBase starts > < t:2024-10-27 18:09:05,695 f:scan_operation_thread.py l:104 c:FullScanOperation...

fix(full scan thread): Added missing fetch-next-page to fetch_result_pages

@yarongilor Please raise an issue for what you found

improvement(tomstone-gc): Added a verification to large-partitions tests

Just don't backport any of those changes to 2023.1 Only to branches that really needs it Since this PR is open for a whole year now, I guess it's not...

Feature zero token nodes

I would recommend adding issues for follow on other backends, we can help with docker/gce/azure, and cloud/operator team with k8s backend, they would need it as well at some point.

feature(jenkins): New jobs with gossip-topology-changes

@aleksbykov is there some place there was a discussion / test plan, which jobs should be duplicated ? (otherwise, what exactly we should be reviewing here ?)

feature(jenkins): New jobs with gossip-topology-changes

@aleksbykov @temichus I never got an answer regarding this PR, is that needed ? it's expected to be part of teir1 ? part of a release testing ? is that...

feature(jenkins): New jobs with gossip-topology-changes

@temichus @aleksbykov, if those are not needed for upcoming releases, please close this PR.

After error: sdcm.remote.base.RetryableNetworkException next command on with same remoter and ssh session could be not executed on node

> I saw the same issue (I think) here: [https://argus.scylladb.com/test/8764d79e-d785-4b99-9c70-99e2f24d0a18/runs?additionalRuns[]=b3091312-ac66-4ca5-86ff-35e1fa8c8dec](https://argus.scylladb.com/test/8764d79e-d785-4b99-9c70-99e2f24d0a18/runs?additionalRuns%5B%5D=b3091312-ac66-4ca5-86ff-35e1fa8c8dec) > > @fruch who should own this? I would expect whom found it during master duty to attend to it,...