Use volatile and AtomicIntegers to be thread safe

Modify the fields in ReplicationState class to be volatile and
AtomicIntegers so that changes to them are reflected to other
threads. By not doing so, modifications made by one thread to
these fields may not be reflected instantly depending on
cpu caching thus resulting in incorrect state

Change-Id: I76512b17c19cc68e4f1e6a5223899f9a184bb549
1 file changed
tree: 68527d26dd607a38d25b03ab49e1c2daa777dbea
  1. .gitignore
  2. .mailmap
  3. .settings/
  4. BUILD
  6. src/