This repository has been archived by the owner on Jul 24, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 43
Must call Poseidon::ConsumerGroup#close when you're done with ConsumerGroup! #20
Comments
In the meantime, I will probably wrap my code as follows:
|
Could you please submit a PR with a test? |
+1 it seems I have the same issue |
I decided to follow the recommendation here just in case. For some reason I get error trying to call consumer.close() in ensure block:
I'm using poseidon_cluster 0.3.2 with ruby 2.2.1 |
@daluu could you prepare a test case? |
It's been a while and I stopped working with poseidon cluster. But on a quick check/test, it seems my issue does not occur now. Not sure what happened before. |
@daluu I cannot reproduce as well. Could you please close the issue then? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem: When I instantiate two consumer groups without calling
#close
, the second ConsumerGroup does not ingest any messages. Here's an example:Output is:
but I expected to see
The only way I can get the expected output is if I call
consumer.close()
in each iteration. This was really surprising and not documented in the README or examples.Perhaps when
consumer
goes out of scope, you could leverage define_finalizer to callclose
to prevent this from happening?The text was updated successfully, but these errors were encountered: