Israel Fruchter comments

Results 978 comments of


                                            Israel Fruchter

dockerd could be restarted on loader for gemini job if several stress tool running on same loader

> > We've seen lots of issues like those, but I'm not sure it's connected to other stress commands running. > > > > I think that we are using...

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

> > Assigning to the drivers team for now. > > [@dkropachev](https://github.com/dkropachev) could you confirm that you agree with Karol's assignment to your team? I prefer to validate as this...

[GCP] N2D Instance Family support

nit: AMI is AWS name for images :)

Export nemesis v2

@roydahan we didn't read the docs: https://docs.python.org/3/library/multiprocessing.html#multiprocessing.set_start_method seems like we should be calling this only once, so maybe put it in a session fixture

Export nemesis v2

@roydahan let's write down what are the expectations, and let someone work on it. I don't see any value in this PR anymore

Export nemesis v2

> I think the hydra CLI is something that @pehala is already doing (or already did). Regarding the MacOS workarounds, I need to check what's needed now. for macos, I...

improvement(fill_db_data): Remove 30s sleep of waiting for schema agreement

@roydahan seems test was failing cause it was missing the extra timeout for the truncate operation. maybe for the safe side, rebase this PR, and try it again ?

Consider replacing syslog-ng with vector.dev

We can do client filtering with syslog-ng We don't know if our bottle neck is syslog-ng, it's probably the fact we are reading all lines in python, and doing a...

Consider replacing syslog-ng with vector.dev

@roydahan you think there is still a need for this one ? is the cloud really completely move to that one ?

Consider replacing syslog-ng with vector.dev

> I don't know, do you think the "bad packet" issue is still caused by our parsing? I preety sure it's not our parsing, just out inability to preserve CPU...