Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 728d670 May 25, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
ui cloud logos in nodes May 18, 2019
.gitignore fixed bug Oct 12, 2018
ini.template Update ini.template Mar 7, 2019 adding failures Dec 21, 2018
priv.key fixing parameter imports Feb 8, 2019
startup adding jshook simple startup Dec 28, 2018 secrtion configs Feb 9, 2019


This demo is to showcase DSE's ability to be continuously available under any circumstance and it has two parts: The Demo application and khaosKatz. The Demo is a simple application that writes data into DSE, but if it misses a single write the application will crash. KhaosKatz will continously load random scenarios taking down different nodes and/or entire datacenters. The goal is to run the Demo application successfully even while khaosKatz starts taking things down ungracefully.

Setup the cluster

  • 2+ DCs, 3+ nodes each
  • Opscenter

Setup the Demo app

(Note: If you installed the AssetHub Multi-Cloud Cluster everything is already setup in /tmp/dse-uptime-demo on the opscenter node. If you don't know what AssetHub is you can safely ignore this note :) )

  demo.ini: Configuration file Script to create demo.ini based on Opscenter Demo application to write data into the cluster Read application to read back data written into the cluster from the writeDemo app Automated Chaos! Simulates different cluster failure scenarios
  • create demo.ini

    • ./ demo.ini opscenter.hostname
  • optional: edit demo.ini

    • Setup SSL/Auth if required
    • Update SSH private keys
    • Change the consistency levels for the applications
    • Change local DCs for the read/write applications

Running the Demo

  • open new terminal and run ./
  • open new terminal and run ./
  • Open new terminal and run ./
    • Select failure scenarios and see how the applications respond!
You can’t perform that action at this time.