This repository has been archived by the owner on Jun 5, 2018. It is now read-only.
Chirp tables may fail to be created if cassandra is not up #24
Labels
Comments
This was referenced Jun 30, 2016
dotta
added a commit
to dotta/lagom
that referenced
this issue
Jun 30, 2016
As highlighted in lagom/lagom-java-chirper-example#24, making sure that a read-side table is (eventually) created can be challenging. In particular, users need to ensure that the create table statement is retried if Cassandra isn't available. This commit addresses the problem by encapsulating the retry logic in a new API class: `CassandraReadSideTableCreator`. Both the number of attempts and the interval between each attempt is configurable.
This was referenced Sep 5, 2016
Merged
|
Nice work! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The chirp table are created as part of the chirp service initialization https://github.com/lagom/activator-lagom-java-chirper/blob/master/chirp-impl/src/main/java/sample/chirper/chirp/impl/ChirpServiceImpl.java#L52-L64. If Cassandra is not up (e.g., it's in the process of being started), then the chirp tables won't be created. To avoid the issue, the table should be created only when a connection with the Cassandra server can be established.
The text was updated successfully, but these errors were encountered: