Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asynchronous call back of redis subscriber not called #1196

Open
Arun210688 opened this issue Jun 15, 2023 · 0 comments
Open

Asynchronous call back of redis subscriber not called #1196

Arun210688 opened this issue Jun 15, 2023 · 0 comments

Comments

@Arun210688
Copy link

Arun210688 commented Jun 15, 2023

I use Hiredis async feature for my publisher subscriber model.

Scenario :
When I execute PUBSUB CHANNELS from redis-cli , i can see all my 5 channels(channel1 to channel5) list.
When I publish an event to the first channel it will publish to 2nd channel , 2nd channel will publish to 3rd channel and it continues up to 5 channels.

Problem:
Most of the times the set up works fine .
But sometimes the message is received only by the 1st channel and get stuck , the callback of 2nd channel is not getting called . Even if I publish fresh data to channel1 , it is received by channel 1 but not cascaded to channel2
I need to completely restart both redis -server and my application to continue work.

Support needed

  1. Can you help understand why the asynchronous call back of channel2 is not invoked. Is there any debug log messages that I can enable to look into the reason .
  2. What all the possibility for this error scenario.
  3. Is there any methods to check if there are any pending messages for a particular channel in the redis server that are not received by the clients.
@Arun210688 Arun210688 changed the title Asynchronous call back of redis publisher not called Asynchronous call back of redis subscriber not called Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant