@rpike,
Thanks for reporting this. The issue was solved for now by restarting a stuck node in our production cluster. We're continuing the investigation to establish root cause so that we can address the issue at its source.
We're sorry for the inconvenience caused while that server was down.
Peter.
