fast-data-dev
fast-data-dev copied to clipboard
Connect HealthCheck failure 85.7%
I've had lots of feedback saying that connect healthcheck is failing. My guess is that because connect takes WAY more time to load right now due to the plugin and classpath changes. Or something else but I'm not so sure
Yes, your guess is correct indeed. I will try to do something about this. Thanks for the feedback!
I added a check in 62dd7786208e122b7ed65ee0da8acd8464fa853c for the connect tests to wait up to 300 seconds for Connect to start —trying their luck every 10 seconds.
I believe usually 2-3 minutes pass until we reach the connect tests, so in total Connect now has about 8 minutes to start before failing the tests.
There are still edge cases that depend on the machine you run fast-data-dev, but I believe you will get much less complaints. :)
sweet! definitely waiting for the endpoint to come online is a good strategy :) Cheers