Oran Agra

@yevhen-harmonizehr please specify which version you're using.

so it can't be the above mentioned fix, which was part of 6.2. if anyone reproduces this again (regardless of the version), we'd love to get some info. see the...

i'd like a stack trace to see what it's doing. you can maybe do that with the instructions here https://github.com/redis/redis/issues/9956#issuecomment-1304445937 or if you're willing to kill the process, then `kill...

thanks. this is useful. @michael-grunder can you take a look? any reason why redisNetRead will eat CPU, or do a blocking read (following an epoll indication that it's readable)?

@michael-grunder can you please take a closer look?

we discussed this in a core-team meeting. we feel it's wrong to let the admin control such things that could affect the application and cause some negative impact (e.g. the...

@sg893052 did it happen once? or does it reproduce. i see this is a rather old version (even for 6.2.x), skimming over the release notes i don't see anything obvious,...

You mean that before 7.0 it was possible to replicate without locking, and now it's not? We can clearly state it in the api docs. However, If it wasn't documented...

is there any reason to use it like that? i.e. any reason to call replicateVerbatim from a thread? maybe before blocking the module can't decide yet if it wants to...

i don't think i understand what new field you refer to. i think we should add a line to document the ones that **are** designed to be thread safe, and...