Versions Compared

Old Version 25

changes.mady.by.user Unknown User (nizhikov)

Saved on

compared with

New Version 26

changes.mady.by.user Unknown User (nizhikov)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Is there rolling upgrade feature?
  2. How it implemented?
  3. How it tested?
  4. When it tested: Each PR? Weekly? Only on release?
  5. Network message format.
  6. Serdes implementation.
  7. How many earlier releases can be upgraded.

Name

Is there rolling upgrade feature?

How it implemented?

How it tested?

When it tested?

Network message format

Serdes implementation

How many earlier releases can be upgraded?

Apache CassandraYes (1), (2)Server-client compatibility works similar to Ignite Thin Client protocol.

Compatibility checked with the special test framework (3)
At a first glance, there are no special source code checks to ensure compatibility in day by day coding

On release or by requestPOJOCustom serdes implementation.
Apache KafkaYes (4)

Message formats checked on PR reivew. 
At a first glance, there are no special source code checks to ensure compatibility in day by day coding.
But, all machinery to code compatible implemented in code generation framework (5)

Compatibility checked with the special test framework ducktest (6)

On release or by request.
Kafka doesn't provide public resources to run ducktests. Run done by contributors or by confluent employers on private hosts

POJOCustom serdes implementation.All
YugabyteYes (7)

checked on review (see commit message section "Upgrade/Rollback safety") (8)



plain objectsProtobuf
YDBYes

Message formats checked on PR rivew - grpc+protobuf helps to maintain compatibility

Compatibility checked with the special test framework (9)

On request.

plain objectsProtobuf
Cockroach DBYes




plain objectsProtobuf
HazelcastYes








Description

Rolling Upgrade assumes that cluster can consist of Ignite nodes of different versions.
So Ignite must provide backward compatibility on network level and ability to work in mixed topology.
Development time checks, tests must be added to provide protection of incorrect patches.
Ignite codebase must be reorganized in a way to clearly distinguish those parts that require compatibility and those who don't.

Let's define clearly, what backward compatibility for the network messages means:

...