kafka) kafka cluster 설정

 

이전 포스팅에서 zookeeper cluster 생성했고

kafka) zookeeper cluster 설정하기

이제 kafka cluster 세팅해야해요

 

예상 독자

1. kafka cluster 설정하려고 하는 분
2. 미래의 나

요약

1. kafka다운로드
2. 설정 변경
3. 실행/중지

설명

1. Kafka 다운로드

다운로드 받아서 압축 풀기: https://archive.apache.org/dist/kafka/3.1.1/kafka_2.13-3.1.1.tgz\

binrary 압축 해제

cd /home/kafka 
# kafka 3.1.1
wget https://archive.apache.org/dist/kafka/3.1.1/kafka_2.13-3.1.1.tgz
tar xzf kafka_2.13-3.1.1.tgz
mv kafka_2.13-3.1.1 kafka
chown -R kafka:kafka kafka
chmod -R 755 kafka

2. 설정 변경

java 11 다운로드가 필요해요

• 3.0.0 : The deprecation of support for Java 8 and Scala 2.12
• CMAK -> Java 11이상 지원

/bin/kafka-run-class.sh

# JDK 11 use
JAVA_HOME=/home/manager/jdk-11.0.2

/bin/kafka-server-start.sh

export JMX_PORT=9999 설정

 

#!/bin/bash
export JMX_PORT=9999

if [ $# -lt 1 ];
then
        echo "USAGE: $0 [-daemon] server.properties [--override property=value]*"
        exit 1
fi
base_dir=$(dirname $0)

if [ "x$KAFKA_LOG4J_OPTS" = "x" ]; then
    export KAFKA_LOG4J_OPTS="-Dlog4j.configuration=file:$base_dir/../config/log4j.properties"
fi

if [ "x$KAFKA_HEAP_OPTS" = "x" ]; then
    export KAFKA_HEAP_OPTS="-Xmx1G -Xms1G"
fi

EXTRA_ARGS=${EXTRA_ARGS-'-name kafkaServer -loggc'}
export AUTH_ARGS=${AUTH_ARGS-'-Djava.security.auth.login.config=file:/home/manager/kafka/config/kafka_server_jaas.conf'}
COMMAND=$1
case $COMMAND in
  -daemon)
    EXTRA_ARGS="-daemon "$EXTRA_ARGS
    shift
    ;;
  *)
    ;;
esac

#exec $base_dir/kafka-run-class.sh $EXTRA_ARGS $AUTH_ARGS  kafka.Kafka  "$@"
exec $base_dir/kafka-run-class.sh $EXTRA_ARGS  kafka.Kafka  "$@"

config/server.properties

1. (필수) broker.id
2. (필수) listeners
3. advertised.listeners 
4. listener.security.protocol.map
5. inter.broker.listener.name
6. log.dirs
7. (필수) zookeeper.connect

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.

broker.id=0

############################# Socket Server Settings #############################

# The address the socket server listens on. It will get the value returned from

# java.net.InetAddress.getCanonicalHostName() if not configured.

#   FORMAT:

#     listeners = listener_name://host_name:port

#   EXAMPLE:

#     listeners = PLAINTEXT://your.host.name:9092

#listeners=PLAINTEXT://:9092

listeners=PLAINTEXT://192.168.10.***:9092 # 여기는 무조건 IP

#listeners=INTERNAL://{내부IP}:9092,EXTERNAL://0.0.0.0:9093

 

api.version.request=false

auto.commit.enable=false

 

delete.topic.enable=true

 

# Hostname and port the broker will advertise to producers and consumers. If not set,

# it uses the value for "listeners" if configured.  Otherwise, it will use the value

# returned from java.net.InetAddress.getCanonicalHostName().

#advertised.listeners=PLAINTEXT://your.host.name:9092

#advertised.listeners=INTERNAL://{내부IP}:9092,EXTERNAL://{외부IP}:9093

#inter.broker.listener.name=INTERNAL

 

# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details

#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

#listener.security.protocol.map=INTERNAL:PLAINTEXT,EXTERNAL:PLAINTEXT

# 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=/tmp/kafka-logs

log.dirs=/home/manager/kafka-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 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

log.retention.hours=120

# 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

zookeeper.connect=kafka0:12181,kafka1:12181,kafka2:12181

# Timeout in ms for connecting to zookeeper

zookeeper.connection.timeout.ms=18000

#4mb

message.max.bytes=15728640

############################# 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

 

3. 시작 & 중지

systemctl로 하면 관리가 오히려 힘들것 같아서

수동으로 실행하고 있음. 

/home/manager/apache/kafka/bin/kafka-server-start.sh\
  -daemon /home/manager/apache/kafka/config/server.properties

/home/manager/apache/kafka/bin/kafka-server-stop.sh