SAMZA-2633: Rolling upgrades cause downtime to upgraded processors for the entire deployment window (#1484)

Description:
During rolling upgrades, the current debounce timer gets extended every time when there is a quorum change notification. As a result, processors that were upgraded earlier in the deployment window remain unavailable waiting for work assignment. In some scenarios, this cause processors to be unavailable for 20 minutes or so depending on the size of the quorum and the debounce time configuration. Refer to SAMZA-2633 for more information.

Changes:
Optimize the leader workflow to skip rebalance if there is no changes to work assignment
Make processors start with most recent agreed job model on startup
Leader persists the active job model version in ZK to enable change [2]
Introduce config for applications to opt-in for the optimization

Usage Instructions:
Set job.coordinator.zk.enable-startup-with-active-job-model to true as part of the application configuration to enable processor use the recent active job model during startup and also enable leader to skip rebalances if the work assignment remains the same.
8 files changed
tree: 70db6991b04ac0f1ab929f70fa0b23a05fc9f25b
  1. .gitignore
  2. .reviewboardrc
  3. .travis.yml
  4. HEADER
  5. KEYS
  6. LICENSE
  7. NOTICE
  8. README.md
  9. RELEASE.md
  10. bin/
  11. bootstrap.gradle
  12. build.gradle
  13. checkstyle/
  14. doap_Samza.rdf
  15. docs/
  16. gradle.properties
  17. gradle/
  18. gradlew
  19. gradlew.bat
  20. samza-api/
  21. samza-aws/
  22. samza-azure/
  23. samza-core/
  24. samza-elasticsearch/
  25. samza-hdfs/
  26. samza-kafka/
  27. samza-kv-couchbase/
  28. samza-kv-inmemory/
  29. samza-kv-rocksdb/
  30. samza-kv/
  31. samza-log4j/
  32. samza-log4j2/
  33. samza-rest/
  34. samza-shell/
  35. samza-sql-shell/
  36. samza-sql/
  37. samza-test/
  38. samza-tools/
  39. samza-yarn/
  40. settings.gradle
  41. sonar-project.properties
README.md

What is Samza? Build Status

Apache Samza is a distributed stream processing framework. It uses Apache Kafka for messaging, and Apache Hadoop YARN to provide fault tolerance, processor isolation, security, and resource management.

Samza's key features include:

  • Simple API: Unlike most low-level messaging system APIs, Samza provides a very simple callback-based “process message” API comparable to MapReduce.
  • Managed state: Samza manages snapshotting and restoration of a stream processor's state. When the processor is restarted, Samza restores its state to a consistent snapshot. Samza is built to handle large amounts of state (many gigabytes per partition).
  • Fault tolerance: Whenever a machine in the cluster fails, Samza works with YARN to transparently migrate your tasks to another machine.
  • Durability: Samza uses Kafka to guarantee that messages are processed in the order they were written to a partition, and that no messages are ever lost.
  • Scalability: Samza is partitioned and distributed at every level. Kafka provides ordered, partitioned, replayable, fault-tolerant streams. YARN provides a distributed environment for Samza containers to run in.
  • Pluggable: Though Samza works out of the box with Kafka and YARN, Samza provides a pluggable API that lets you run Samza with other messaging systems and execution environments.
  • Processor isolation: Samza works with Apache YARN, which supports Hadoop's security model, and resource isolation through Linux CGroups.

Check out Hello Samza to try Samza. Read the Background page to learn more about Samza.

Building Samza

To build Samza from a git checkout, run:

./gradlew clean build

To build Samza from a source release, it is first necessary to download the gradle wrapper script above. This bootstrapping process requires Gradle to be installed on the source machine. Gradle is available through most package managers or directly from its website. To bootstrap the wrapper, run:

gradle -b bootstrap.gradle

After the bootstrap script has completed, the regular gradlew instructions below are available.

Scala and YARN

Samza builds with Scala 2.11 or 2.12 and YARN 2.6.1, by default. Use the -PscalaSuffix switches to change Scala versions. Samza supports building Scala with 2.11 and 2.12.

./gradlew -PscalaSuffix=2.11 clean build

Testing Samza

To run all tests:

./gradlew clean test

To run a single test:

./gradlew clean :samza-test:test -Dtest.single=TestStatefulTask

To run key-value performance tests:

./gradlew samza-shell:kvPerformanceTest -PconfigPath=file://$PWD/samza-test/src/main/config/perf/kv-perf.properties

To run yarn integration tests:

./bin/integration-tests.sh <dir> yarn-integration-tests

To run standalone integration tests:

./bin/integration-tests.sh <dir> standalone-integration-tests

Running checkstyle on the java code

./gradlew checkstyleMain checkstyleTest

Job Management

To run a job (defined in a properties file):

./gradlew samza-shell:runJob -PconfigPath=/path/to/job/config.properties

To inspect a job's latest checkpoint:

./gradlew samza-shell:checkpointTool -PconfigPath=/path/to/job/config.properties

To modify a job's checkpoint (assumes that the job is not currently running), give it a file with the new offset for each partition, in the format systems.<system>.streams.<topic>.partitions.<partition>=<offset>:

./gradlew samza-shell:checkpointTool -PconfigPath=/path/to/job/config.properties \
    -PnewOffsets=file:///path/to/new/offsets.properties

Developers

To get Eclipse projects, run:

./gradlew eclipse

For IntelliJ, run:

./gradlew idea

Contribution

To start contributing on Samza please read Rules and Contributor Corner. Notice that Samza git repository does not support git pull request.

Apache Software Foundation

Apache Samza is a top level project of the Apache Software Foundation.

Apache Software Foundation Logo