Hello and thanks for joining us in this discussion today
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
see JobGenerator.scala
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
see JobGenerator.scala
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
Spark context can be killed with streaming context still running.
Will enter the foreachRDD loop without having any executor available.
saveInitialState(…) LWT protects against this.
If needed could add a synchronization point before: rdd.take(1)
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
So who is DataStax?
We are a 400 people company with offices around the world.
We have validation from some of the worlds leading venture firms
And we are continuing to drive momentum with customers that are the top brands in the world who believe in us
Even Industry influencers like Gartner consistently rank us at the top in multiple categories.
Last year Forbes listed us in the world’s best 100 cloud companies.
Disable unclean leader election
Disable unclean leader election to prevent the election of a leader out of sync (could result in data loss).
This provides balance between consistency (guaranteed message delivery) and availability. With unclean leader election disabled, if a broker containing the leader replica for a partition becomes unavailable, and no in-sync replica exists to replace it, the partition becomes unavailable until the leader replica or another in-sync replica is back online.
unclean.leader.election.enable = false
Replication factor
RF=3 is probably the best choice for this use case
default.replication.factor = 3
Max inflight request (order guarantee)
If the order matters, set the max number of inflight request to 1 (otherwise the first one could fail and the 2nd one succeed)
Max.in.flight.requests.per.connection = 1
Minimum ISRs
Change the minimum in-synch replicas that must be available for the producer to successfully send messages to a partition.
A replica is considered in synch as long as the lag is < Replica.lag.max.messages and the leader received the last fetch within replica.lag.time.max.ms
In newer versions, replica.lag.time.max.ms also put a replica out of synch if he didn’t catch up to the last upset within this duration.
Minimum ISR should be set to 2 to prevent data loss
min.insynch.replicas = 2
Producer acks
Producer should wait for all ISR ack (at least 2) to prevent message lost
acks = all