Skip to main content
Quick navigation

Chaos Simulate Invalid Schema Id

This interceptor injects Schema Ids into messages, simulating a situation where clients cannot deserialize messages with the schema information provided.

This demo will run you through some of these use cases step-by-step.

View the full demo in realtime

You can either follow all the steps manually, or watch the recording

Review the docker compose environment

As can be seen from docker-compose.yaml the demo environment consists of the following services:

  • gateway1
  • gateway2
  • kafka-client
  • kafka1
  • kafka2
  • kafka3
  • schema-registry
  • zookeeper
cat docker-compose.yaml

Starting the docker environment

Start all your docker processes, wait for them to be up and ready, then run in background

  • --wait: Wait for services to be running|healthy. Implies detached mode.
  • --detach: Detached mode: Run containers in the background
docker compose up --detach --wait

Creating virtual cluster teamA

Creating virtual cluster teamA on gateway gateway1 and reviewing the configuration file to access it

# Generate virtual cluster teamA with service account sa
token=$(curl \
--request POST "http://localhost:8888/admin/vclusters/v1/vcluster/teamA/username/sa" \
--header 'Content-Type: application/json' \
--user 'admin:conduktor' \
--silent \
--data-raw '{"lifeTimeSeconds": 7776000}' | jq -r ".token")

# Create access file
echo """
bootstrap.servers=localhost:6969
security.protocol=SASL_PLAINTEXT
sasl.mechanism=PLAIN
sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username='sa' password='$token';
""" > teamA-sa.properties

# Review file
cat teamA-sa.properties

Creating topic with-schema on teamA

Creating on teamA:

  • Topic with-schema with partitions:1 and replication-factor:1
kafka-topics \
--bootstrap-server localhost:6969 \
--command-config teamA-sa.properties \
--replication-factor 1 \
--partitions 1 \
--create --if-not-exists \
--topic with-schema

Adding interceptor simulate-invalid-schema-id

Let's create the interceptor against the virtual cluster teamA, instructing Conduktor Gateway to inject Schema Ids into messages, simulating a situation where clients cannot deserialize messages with the schema information provided.

Creating the interceptor named simulate-invalid-schema-id of the plugin io.conduktor.gateway.interceptor.chaos.SimulateInvalidSchemaIdPlugin using the following payload

{
"pluginClass" : "io.conduktor.gateway.interceptor.chaos.SimulateInvalidSchemaIdPlugin",
"priority" : 100,
"config" : {
"topic" : "with-schema",
"invalidSchemaId" : 999,
"target" : "CONSUME"
}
}

Here's how to send it:

curl \
--request POST "http://localhost:8888/admin/interceptors/v1/vcluster/teamA/interceptor/simulate-invalid-schema-id" \
--header 'Content-Type: application/json' \
--user 'admin:conduktor' \
--silent \
--data @step-07-simulate-invalid-schema-id.json | jq

Listing interceptors for teamA

Listing interceptors on gateway1 for virtual cluster teamA

curl \
--request GET 'http://localhost:8888/admin/interceptors/v1/vcluster/teamA' \
--header 'Content-Type: application/json' \
--user 'admin:conduktor' \
--silent | jq

Let's produce some records to our created topic

echo '{"message": "hello world"}' | \
kafka-json-schema-console-producer \
--bootstrap-server localhost:6969 \
--topic with-schema \
--producer.config teamA-sa.properties \
--property value.schema='{
"title": "someSchema",
"type": "object",
"properties": {
"message": {
"type": "string"
}
}
}'

Let's consume them with a schema aware consumer.

kafka-json-schema-console-consumer \
--bootstrap-server localhost:6969 \
--topic with-schema \
--consumer.config teamA-sa.properties \
--from-beginning

Tearing down the docker environment

Remove all your docker processes and associated volumes

  • --volumes: Remove named volumes declared in the "volumes" section of the Compose file and anonymous volumes attached to containers.
docker compose down --volumes

Conclusion

Yes, Chaos Simulate Invalid Schema Id is simple as it!