version
springboot version | 2.1.5.RELEASE |
kafka version | 2.2 |
Encountered pit
- With the latest springboot kafka will use the latest version!
- When I started zk on the cloud service, and then start kafka no problem, then springboot connection kafka project, there is always warn level log: "Connection to node -1 could not be established Broker may not be available.."
- springboot project console throws exception ip address is not legitimate, as compared with the above problem, not the same problem.
telnet at 9092 port cloud server is not responding, and then look at the cloud server security group was also added ah, in the end Editor's Note?
The original issue kafka profile will kafka server configuration file amended as follows:
Note that the following three red configuration is very important to solve all my problems!
advertised.host.name must write ip address kafka server ! If the write server localhost, and the project running and not running the same server kafka, it will not connect.
############################# Server Basics ################### ########## # of the ID of the Broker. This MUST BE a uNIQUE SET to Integer for each Broker. globally unique number #broker can not be repeated Broker. ID = 0 ####### ###################### Socket Server Settings ######################### #### # listening port in the listeners = PLAINTEXT: //: 9092 # ip address of the client connections must be written ip address of the server! advertised.host.name advertised.host.name = 47.XX.XX.XX host.name = localhost # Maps listener names to Security Protocols, at The default IS for Them at The Same, to BE. See at The config Documentation for More details #listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL # The number of threads that the server uses for receiving requests from the network and sending responses to the network num.network.threads=3 # The number of threads that the server uses for processing requests, which may include disk I/O num.io.threads=8 # The send buffer (SO_SNDBUF) used by the socket server socket.send.buffer.bytes=102400 # The receive buffer (SO_RCVBUF) used by the socket server socket.receive.buffer.bytes=102400 # The maximum size of a request that the socket server will accept (protection against OOM) socket.request.max.bytes=104857600 ############################# Log Basics ############################# # A comma separated list of directories under which to store log files log.dirs=/root/mysoftware/kafka_2.12-2.2.0/logs # The default number of log partitions per topic. More partitions allow greater # parallelism for consumption, but this will also result in more files across # the brokers. num.partitions=1 # The number of threads per data directory to be used for log recovery at startup and flushing at shutdown. # This value is recommended to be increased for installations with data dirs located in RAID array. num.recovery.threads.per.data.dir=1 ############################# Internal Topic Settings ############################# # The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state" # For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3. offsets.topic.replication.factor=1 transaction.state.log.replication.factor=1 transaction.state.log.min.isr=1 ############################# Log Flush Policy ############################# # Messages are immediately written to the filesystem but by default we only fsync() to sync # the OS cache lazily. The following configurations control the flush of data to disk. # There are a few important trade-offs here: # 1. Durability: Unflushed data may be lost if you are not using replication. # 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush. # 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks. # The settings below allow one to configure the flush policy to flush data after a period of time or # every N messages (or both). This can be done globally and overridden on a per-topic basis. # The number of messages to accept before forcing a flush of data to disk #log.flush.interval.messages=10000 # The maximum amount of time a message can sit in a log before we force a flush #log.flush.interval.ms=1000 ############################# Log Retention Policy ############################# # The following configurations control the disposal of log segments. The policy can # be set to delete segments after a period of time, or after a given size has accumulated. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens # from the end of the log. # The minimum age of a log file to be eligible for deletion due to age log.retention.hours=168 # A size-based retention policy for logs. Segments are pruned from the log unless the remaining # segments drop below log.retention.bytes. Functions independently of log.retention.hours. #log.retention.bytes=1073741824 # The maximum size of a log segment file. When this size is reached a new log segment will be created. log.segment.bytes=1073741824 # The interval at which log segments are checked to see if they can be deleted according # to the retention policies log.retention.check.interval.ms=300000 ############################# Zookeeper ############################# # Zookeeper connection string (see zookeeper docs for details). # This is a comma separated host:port pairs, each corresponding to a zk # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002". # You can also append an optional chroot string to the urls to specify the # root directory for all kafka znodes. zookeeper.connect=localhost:2181 # Timeout in ms for connecting to zookeeper zookeeper.connection.timeout.ms=6000 ############################# Group Coordinator Settings ############################# # The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance. # The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms. # The default value for this is 3 seconds. # We override this to 0 here as it makes for a better out-of-the-box experience for development and testing. # However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup. group.initial.rebalance.delay.ms=0
Code
pom.xml
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.1.5.RELEASE</version> <relativePath/> <!-- lookup parent from repository --> </parent> <groupId>xy.study</groupId> <artifactId>kafka-demo</artifactId> <version>0.0.1-SNAPSHOT</version> <name>kafka-demo</name> <description>Kafka demo project for Spring Boot</description> <properties> <java.version>1.8</java.version> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter</artifactId> </dependency> <dependency> <groupId>org.springframework.kafka</groupId> <artifactId>spring-kafka</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-devtools</artifactId> <scope>runtime</scope> </dependency> <dependency> <groupId>com.alibaba</groupId> <artifactId>fastjson</artifactId> <version>1.2.47</version> </dependency> <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <optional>true</optional> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.springframework.kafka</groupId> <artifactId>spring-kafka-test</artifactId> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>
application.properties
=================== ============== kafka # # kafka designated proxy address, multiple spring.kafka.bootstrap - = 47.XX.XX.XX Servers: 9092 # =============== Provider ====================== = spring.kafka.producer.retries = 0 # number of messages transmitted per batch spring.kafka.producer.batchSize = 16384 spring.kafka.producer.bufferMemory = 33554432 codec # specified message key and the message body spring.kafka .producer.key -serializer = org.apache.kafka.common.serialization.StringSerializer spring.kafka.producer.value -serializer = org.apache.kafka.common.serialization.StringSerializer # ========== ===== consumer ======================= # Specify the default consumer the above mentioned id Group spring.kafka.consumer.group -id = Consumer-Group- the Test spring.kafka.consumer.auto -offset is either-the RESET = Earliest spring.kafka.consumer.enable -auto-the commit = to true the Spring. kafka.consumer.auto the -commit-interval the 100 = # codec specified message key and the message body spring.kafka.consumer.key -deserializer = org.apache.kafka.common.serialization.StringDeserializer spring.kafka.consumer.value -deserializer = org.apache.kafka.common.serialization.StringDeserializer
Producers and consumers
@Component @Slf4j public class KafkaProducer { @Autowired private KafkaTemplate<String, String> kafkaTemplate; public void sendADotaHero() { DotaHero dotaHero = new DotaHero("虚空假面", "敏捷", "男"); ListenableFuture<SendResult<String, String>> future = kafkaTemplate.send(KafkaTopic.A_DOTA_HERO, JSONObject.toJSONString(dotaHero)); future.addCallback(new ListenableFutureCallback<SendResult<String, String>>() { @Override public void onFailure(Throwable throwable) { log.error("kafka sendMessage error, throwable = {}, topic = {}, data = {}", throwable, KafkaTopic.A_DOTA_HERO, dotaHero); } @Override public void onSuccess(SendResult<String, String> stringDotaHeroSendResult) { log.info("kafka sendMessage success topic = {}, data = {}",KafkaTopic.A_DOTA_HERO, dotaHero); } }); log.info("kafka sendMessage end"); } }
@Slf4j @Component public class KafkaConsumer { @KafkaListener(topics = KafkaTopic.A_DOTA_HERO, groupId = "${spring.kafka.consumer.group-id}") private void kafkaConsumer(ConsumerRecord<String, DotaHero> consumerRecord) { log.info("kafkaConsumer: topic = {}, msg = {}", consumerRecord.topic(), consumerRecord.value()); } }
@Data @AllArgsConstructor @NoArgsConstructor public class DotaHero { Private String name; Private String kind; Private String Sex; / ** * returns a different array elements * @return * / public static List <DotaHero> bulidDiffObjectList () { List <DotaHero > List = new new the ArrayList <> (); List.add ( new new DotaHero ( "shadow magic", "quick", "M" )); List.add ( new new DotaHero ( "black", "quick", "female " )); list.add(newDotaHero ( "Mars", "power", "male" )); return List; } }
public class KafkaTopic { public static final String A_DOTA_HERO = "a_dota_hero"; private KafkaTopic() { } }
test
When finished springboot project started, and then run the test starts Manufacturer:
@Slf4j @RunWith(SpringRunner.class) @SpringBootTest public class KafkaDemoApplicationTests { @Autowired private KafkaProducer kafkaProducer; private Clock clock = Clock.systemDefaultZone(); private long begin; private long end; @Before public void init(){ begin = clock.millis(); } @Test public void send(){ kafkaProducer.sendADotaHero(); } @After public void end(){ end = clock.millis(); log.info("Spend {} millis .", end-begin); } }