This will log and then go on as if nothing happened, that is not what we want.
The failure is logged as ERROR Processor killed after persistence failure...
We could probably improve that error message by including the message from the cause.

Anyway, what to do in the ClusterSharding when this happens is an interesting question. First idea that comes to my mind is that we should watch the coordinator and start a new instance after a while.