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
There seems to be a configuration parameter refreshShardsNumberAfterMin which, if not set, defaults to null and causes a NullPointerException after the daemon runs for a few minutes. However, I didn't see this in the README anywhere. This ended up biting us, so maybe this should be documented to save others the trouble? Some other things that would be helpful:
It'd be nice if the autoscaling daemon failed early with a helpful error message if the configuration isn't right. This would have saved us a lot of time.
When a StreamMonitor fails, it'd be helpful if it printed a stack trace to make debugging what went wrong easier. I ended up adding a line just above here to log the exception from the failed StreamMonitor, which helped me debug my issue.
Let me know what you think, thanks!
-Josh
The text was updated successfully, but these errors were encountered:
Apologies for this - missed that out of the documentation. Version .9.3.1 fixes this in the readme, and also adds defaults for this value (10 minutes) and for region (us-east-1).
There seems to be a configuration parameter
refreshShardsNumberAfterMin
which, if not set, defaults tonull
and causes aNullPointerException
after the daemon runs for a few minutes. However, I didn't see this in the README anywhere. This ended up biting us, so maybe this should be documented to save others the trouble? Some other things that would be helpful:StreamMonitor
fails, it'd be helpful if it printed a stack trace to make debugging what went wrong easier. I ended up adding a line just above here to log the exception from the failed StreamMonitor, which helped me debug my issue.Let me know what you think, thanks!
-Josh
The text was updated successfully, but these errors were encountered: