Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Xandra instead of CQEx in Trigger Engine #459

Open
Pavinati opened this issue Sep 14, 2020 · 1 comment · May be fixed by #837
Open

Use Xandra instead of CQEx in Trigger Engine #459

Pavinati opened this issue Sep 14, 2020 · 1 comment · May be fixed by #837
Labels
app:trigger_engine This issue or pull request is about astarte_trigger_engine application bug Something isn't working
Milestone

Comments

@Pavinati
Copy link
Collaborator

In a setup where trigger engine is connected to a pool of cassandra nodes, whenever any of the cassandra nodes becomes unavailable, Trigger Engine crashes and restarts until the said node becomes available again

@Pavinati Pavinati added bug Something isn't working app:trigger_engine This issue or pull request is about astarte_trigger_engine application labels Sep 14, 2020
@rbino
Copy link
Collaborator

rbino commented Jan 17, 2023

This should be fixed once we use Xandra instead of CQEx

@rbino rbino changed the title Trigger Engine crash when any of the cassandra nodes are not available Use Xandra instead of CQEx in Trigger Engine Jan 17, 2023
@rbino rbino modified the milestones: v1.3, v1.2 Jan 17, 2023
@bettio bettio modified the milestones: v1.2, v1.3 Jun 19, 2023
@noaccOS noaccOS linked a pull request Aug 22, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app:trigger_engine This issue or pull request is about astarte_trigger_engine application bug Something isn't working
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants