Connection status for workers in distributed mode
See original GitHub issueWhen locust runs in --worker
mode it doesn’t say anything about the connection to master.
This can be hard to debug when the workers can’t connect to the master, because it doesn’t validate the connection at all.
Describe the solution you’d like
A log message for the workers saying that it’s connected via tcp://1.2.3.4 etc, and that it should fail if connection doesn’t work, or at least print a warning/error message about it.
Describe alternatives you’ve considered
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Kafka Connect Concepts | Confluent Documentation
Distributed Workers Distributed mode provides scalability and automatic fault tolerance for Kafka Connect. In distributed mode, you start many worker processes ...
Read more >Running Kafka Connect - Standalone vs Distributed Mode ...
To review, Kafka connectors, whether sources or sinks, run as their own JVM processes called “workers”. As mentioned, there are two ways workers...
Read more >Kafka Connect connection | Lenses.io Docs
How to configure Kafka Connect and Lenses for visibility, observability and monitoring. ... Lenses supports only workers running in distributed mode.
Read more >List All the Kafka connect workers running in a group in ...
When a worker leaves, or joins, a Kafka Connect cluster the tasks get rebalanced automatically. Therefore you should only need to monitor ...
Read more >HowTo: Kafka Connect - Kidong Lee - Medium
cd $KAFKA_HOME;# start connect in distributed mode. bin/connect-distributed connect-conf/worker.properties;. Now, Kafka Connect Cluster is installed and is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am currently stuck setting up locust workers and no error is logged.
+1 for logging connection attempts and failures
PS: the master might also log if the server port has been successfully bound and is ready to accept connections from the workes.
Good idea 👍