How can we call the runTask method inside PlayGroundService for our POST call endpoint. i want to reduce the number of DB calls and lock the functionality of POST endpoint.
Quick question: Is there a way, how we can identify the instance that has acquired a specific lock from redis ? There can be consumers across different instances that may have acquired these locks, so identifying the source IP/instance info can help in solving some usecases.
@@mirza_2023 the question is mainly to have a way to retrieve the list of locks acquired by an instance via application logic in code. This can be helpful when we want to gracefully shut down individual instances based on any locks being acquired or not. Spring integration with redis provides a way to get lock registry uuid which is unique to an instance. So, I am looking something similar to this at framework/lib level. Anyways I think, we may have to maintain this list somewhere at instance level to solve this.
How does redis handle concurrent writes internally? Could you point me to some resource? I need to understand how redis ensures race condition does not occur when two clients tries to write to same key simultaneously.
Redis handles its operations sequentially, so you do not need to worry about it, it should not be possible for it to write same two keys at the same time
How can we call the runTask method inside PlayGroundService for our POST call endpoint. i want to reduce the number of DB calls and lock the functionality of POST endpoint.
Quick question: Is there a way, how we can identify the instance that has acquired a specific lock from redis ? There can be consumers across different instances that may have acquired these locks, so identifying the source IP/instance info can help in solving some usecases.
You could add that info to the technical logs, so have instance IID and log it when it gets the lock
@@mirza_2023 the question is mainly to have a way to retrieve the list of locks acquired by an instance via application logic in code. This can be helpful when we want to gracefully shut down individual instances based on any locks being acquired or not. Spring integration with redis provides a way to get lock registry uuid which is unique to an instance. So, I am looking something similar to this at framework/lib level. Anyways I think, we may have to maintain this list somewhere at instance level to solve this.
You did not mention how RedisTemplate was autowired
How does redis handle concurrent writes internally? Could you point me to some resource? I need to understand how redis ensures race condition does not occur when two clients tries to write to same key simultaneously.
Redis handles its operations sequentially, so you do not need to worry about it, it should not be possible for it to write same two keys at the same time
@@liliumbosniacumcode Yes. But how? Any doc you can refer to check on the internal mechanism of concurrency handling done by redis.
@@lankesh870 redis.io/docs/manual/transactions/
Hi, this is a very useful redis series, can you guide HOW TO EXPIRE ALL KEYS VALUE IN REDIS. Thank you very much.
As far as I know there is no way to expire keys in bulk, you would need to do it one by one
redis.io/commands/expire
Hi, could you please show us the implementation of lru and lfu cache ?
This one is tough for me to understand :(
Sad :(