Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Improve logging when CassandraEventLog stops itself due to errors when writing #379

Open
volkerstampa opened this issue Jan 27, 2017 · 0 comments
Labels

Comments

@volkerstampa
Copy link
Contributor

When the CassandraEventLog gives up retrying a failed write it stops itself. As a consequence all event-sourced components connected to this log stop themselves. The error logging could be improved in that case: the event log could add some information about the events to be written and the components could log why they are stopping.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant