我正在尝试用docker compose自动扩展JavaSpring框架kafka消费者 --scale
在docker-compose.yaml中标记和转发端口,如“8070-8072:8070”。所以当我触发endpoint来发布消息时,它做得很好。但在消费者端,只有一个消费者消费所有消息。我有3个消费者具有相同的组id和不同的客户端id。我想要的是一个分布式消息传递。我读了一些关于分区的文章,并查阅了日志。好像只有一个分区。这是原因吗?我怎样才能做到这一点?我将添加log、consumer config、publisher config和docker compose文件。首先是日志。似乎只有三个有分区。
命令:
docker-compose up --build --scale nonwebapp=3 --scale webapp=3
docker-compose.yaml文件
kafka:
image: confluentinc/cp-kafka:latest
depends_on:
- zookeeper
ports:
- 9092:9092
environment:
KAFKA_LOG_DIRS: "/kafka/kafka-logs"
KAFKA_BROKER_ID: 1
KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:29092,PLAINTEXT_HOST://localhost:9092
KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT
KAFKA_INTER_BROKER_LISTENER_NAME: PLAINTEXT
KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 3
KAFKA_AUTO_CREATE_TOPICS_ENABLE: "true"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
restart: always
webapp:
build: benchmark.web
command: bash -c "while !</dev/tcp/kafka/29092; do >&2 echo 'Waiting for kafka to up...' sleep 1; done;"
ports:
- "8070-8072:8070"
volumes:
- ./logs:/logs
- ${GCP_KEY_PATH}:/root/keys/keyfile.json:ro
depends_on:
- kafka
environment:
SPRING_KAFKA_BOOTSTRAPSERVERS: kafka:29092
TZ: "Asia/Istanbul"
GOOGLE_APPLICATION_PROJECT_ID: apt-cubist-282712
GOOGLE_APPLICATION_CREDENTIALS: /root/keys/keyfile.json
restart: always
nonwebapp:
build: benchmark.nonweb
command: bash -c "while !</dev/tcp/kafka/29092; do >&2 echo 'Waiting for kafka to up...' sleep 1; done;"
depends_on:
- kafka
volumes:
- ${GCP_KEY_PATH}:/root/keys/keyfile.json:ro
ports:
- "8060-8062:8060"
environment:
SPRING_KAFKA_BOOTSTRAPSERVERS: kafka:29092
GOOGLE_APPLICATION_PROJECT_ID: apt-cubist-282712
GOOGLE_APPLICATION_CREDENTIALS: /root/keys/keyfile.json
TZ: "Asia/Istanbul"
restart: always
生产者配置
@Bean
ProducerFactory<String, byte[]> producerFactory(){
Map<String, Object> configProps = new HashMap<>();
configProps.put(
ProducerConfig.BOOTSTRAP_SERVERS_CONFIG,
kafkaInContainerAdress);
/*
configProps.put(
ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG,
kafkaInLocal);
* /
configProps.put(
ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG,
StringSerializer.class
);
configProps.put(
ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG,
ByteArraySerializer.class
);
return new DefaultKafkaProducerFactory<>(configProps);
}
@Bean
public KafkaTemplate<String,byte[]> kafkaTemplate(){
return new KafkaTemplate<>(producerFactory());
}
消费者配置
@Bean
public ConsumerFactory<String, byte[]> consumerFactory() {
Map<String, Object> props = new HashMap<>();
props.put(
ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG,
kafkaInContainerAdress);
/*
props.put(
ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG,
kafkaInLocal);
* /
props.put(ConsumerConfig.PARTITION_ASSIGNMENT_STRATEGY_CONFIG,
"org.apache.kafka.clients.consumer.RoundRobinAssignor");
props.put(ConsumerConfig.CLIENT_ID_CONFIG, r.nextInt());
props.put(
ConsumerConfig.KEY_DESERIALIZER_CLASS_CONFIG,
StringDeserializer.class);
props.put(
ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG,
ByteArrayDeserializer.class);
props.put("group.id","topic_trial_consumers");
return new DefaultKafkaConsumerFactory<>(props);
}
@Bean
public ConcurrentKafkaListenerContainerFactory<String, byte[]>
kafkaListenerContainerFactory() {
ConcurrentKafkaListenerContainerFactory<String, byte[]> factory =
new ConcurrentKafkaListenerContainerFactory<>();
factory.setConsumerFactory(consumerFactory());
return factory;
}
1条答案
按热度按时间z9gpfhce1#
好像只有一个分区。这是原因吗?
是的,如果只有一个分区,则只有一个使用者(来自使用者组)可以使用它,而其他使用者(来自同一组)即使启动也将处于空闲状态。
似乎只有三个有分区
从你的照片中,我可以看出
topic_trial-0
. 所以它是topic_trial
的第一个分区。例如,将分区的数量增加到3,并启动三个具有相同分区的使用者
group.id
负载应该是分布式的(每个分区一个)。