You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a beautiful day as other days when I use multiprocessing to get data from a topic that has only one partition.
I divided the offsets range by 500 proccesses to process.
Everything seems okay when I get message from one broker nodes, but when I declare 3 nodes in codes like bellow:
consumer_init = KafkaConsumer(
auto_offset_reset='earliest',
group_id='Client3',
bootstrap_servers='*01..com.vn:9092, *02..com.vn:9092, *03..com.vn:9092', #This not works
#bootstrap_servers='*01..com.vn:9092', #This works
value_deserializer=lambda x: x.decode('utf-8')
)
I'm not be able to pull all of the messages. At a random time, the Consumer return "No Broker Available" Error.
When limit down to 200 processes and declare 3 nodes on consumer to get data, there's no more "No Broker Available" output.
I believe it is the issue that match with #2281 @dpkp please have a look
The text was updated successfully, but these errors were encountered:
It's a beautiful day as other days when I use multiprocessing to get data from a topic that has only one partition.
I divided the offsets range by 500 proccesses to process.
Everything seems okay when I get message from one broker nodes, but when I declare 3 nodes in codes like bellow:
consumer_init = KafkaConsumer(
auto_offset_reset='earliest',
group_id='Client3',
bootstrap_servers='*01..com.vn:9092, *02..com.vn:9092, *03..com.vn:9092', #This not works
#bootstrap_servers='*01..com.vn:9092', #This works
value_deserializer=lambda x: x.decode('utf-8')
)
I'm not be able to pull all of the messages. At a random time, the Consumer return "No Broker Available" Error.
When limit down to 200 processes and declare 3 nodes on consumer to get data, there's no more "No Broker Available" output.
I believe it is the issue that match with #2281
@dpkp please have a look
The text was updated successfully, but these errors were encountered: