kafka-down-test.md

• vstart
• create bucket:

~/go/bin/hsbench -a 0555b35654ad1656d804 -s h7GhxuBLTrlhVUyxSPUKUV8r/2EI4ngqJxD7iBdBYLhwluN30JaT3Q== \
  -u http://localhost:8000 -bp bk -b 1 -r default -m i

• create kafka topic:

aws --region=default --endpoint-url http://localhost:8000 sns create-topic --name=fishtopic \
  --attributes='{"push-endpoint": "kafka://localhost"}'

• create notification:

 aws --region=default --endpoint-url http://localhost:8000 s3api put-bucket-notification-configuration \
   --bucket bk000000000000 --notification-configuration='{"TopicConfigurations": [{"Id": "notif1", "TopicArn": "arn:aws:sns:default::fishtopic", "Events": []}]}'

• run test:

~/go/bin/hsbench -a 0555b35654ad1656d804 -s h7GhxuBLTrlhVUyxSPUKUV8r/2EI4ngqJxD7iBdBYLhwluN30JaT3Q== \
  -u http://localhost:8000 -bp bk -m pd -t 16 -z 1K -l 100

• kill kafka mid test (and resume)
• to make sure that idleness is not detected due to the broker down, run vstart with:

MON=1 OSD=1 MDS=0 MGR=0 RGW=1 ../src/vstart.sh -n -d -o rgw_kafka_connection_idle=30