mck

Increasing RF to 3+ is important in production. But I don't know what's best way to do that without breaking dev environments. Currently there is the warning printed, ref https://github.com/openzipkin/zipkin/blob/master/zipkin-storage/cassandra/src/main/java/zipkin/storage/cassandra/Schema.java#L43

Other important things to do to a problem environment are - disable assertions (remove "-ea" from cassandra-env.sh) - run Java8 and G1GC - have all Cassandra and Zipkin servers sync...

all the "java cql driver" metrics should be available, since the Zipkin server uses dropwizard metrics (afaik).

As a workaround in the meantime, you can adjust the intensity of all running repairs to back them off during such windows.

Thanks @jordanwilson230 Indeed the output need to be cleaned up a bit. Some work was recently done to standardise the REST outputs: only resource queries return json entities and commands...

> @michaelsembwever I've managed to build successfully (the only thing bower been needed to be installed globally through npm i -g bower. That should be stated somewhere in docs). Indeed....

@gutsal-arsen correct that's a misconfiguration/incorrect setup of the Cassandra service. Offline (as I'll be asleep the next 8hrs), the easiest way to help you would be to, look into how...

For the non-127.0.0.1 nodes you need to set environment variable as `LOCAL_JMX=no` This is otherwise defined in Cassandra's `cassandra-env.sh`. Also see https://github.com/thelastpickle/cassandra-reaper/blob/master/src/server/src/test/resources/README.md

fixed (snoozed) @gutsal-arsen . if you're making progress i'm happy. i don't know how to change the "Time Left" field on the gitcoin page, will ask support.

> Since env preparation takes too much time, may I use Docker layer caching? I don't know enough about Docker layer caching. Is it a premium feature? Otherwise, anything to...