An error message is logged every second when startup of split client fails

[tom-mi]

We are currently adding split.io to one of our backend services, but we don't have the API key yet, so we added a dummy value. Upon startup of the container, we observed a huge amount of error logs like this:

RefreshableSplitFetcher failed: Problem fetching splitChanges: Could not retrieve splitChanges; http return code 400

This log message is repeated every second (causing quota issues with our logging solution). We assume that the problematic place in the code is in SyncManagerImp.start(), where upon receiving any exception, there is only a sleep of 1000ms and then a retry is performed.

The expected behavior would be to have some kind of exponential backoff in place, so that ever if Split.io is down or returns an error, our services can start up without producing tons of error logs.

Thx for having a look!