2.1 실습용 카프카 브로커 설치
VM 환경
Name: spark_mingeon_kafka-test
CentOS
Memory8 GiB
Cores 4
IP Addresses172.17.19.20
1. Java 설치
$ sudo yum install -y java-1.8.0-openjdk-devel.x86_64완료시 Complete! 출력
2. 주키퍼, 카프카 브로커 실행
// wget(Web GET) install
yum install wget
// make dir
mkdir kafka
cd kafka
// install
wget https://archive.apache.org/dist/kafka/2.5.0/kafka_2.12-2.5.0.tgz
// 압축 해제
tar xvf kafka_2.12-2.5.0.tgz
cd kafka_2.12-2.5.0c: 파일 압축
x: 파일 압축 해제
v: 압축 또는 해제 시 파일 리스트 출력
f: 압축될 파일명 지정
t: 압축된 파일 리스트 보기
z: gzip을 사용해 압축 (그냥 tar보다 압축률이 좋음)
카프카 브로커 실행 옵션 설정
config/server.properties : 카프카 브로커가 클러스터 운영에 필요한 옵션.
실습용 카프카 브로커를 실행할 것이므로 advertised.listener만 설정. (하단 코드 (3)에 해당)
advertised.listener는 카프카 클라이언트 또는 커맨드 라인 툴을 브로커와 연결할 때 사용.
이미 실행되고 있는 카프카 브로커의 설정을 변경하고 싶다면 브로커를 재시작해야 한다.
// 편집기 실행
vi config/server.properties
============= Server Basics =============
Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# see kafka.server.KafkaConfig for additional details and defaults
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
// =============== (1) ===============
실행하는 카프카 브로커의 번호.
단 하나뿐인(unique) 번호로 설정(동일한 id를 가질 경우 비정상적인 동작이 발생 할 수 있다.)
############################# 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
// =============== (2) ===============
카프카 브로커가 통신을 위해 열어둘 인터페이스 IP,port,프로토콜 설정.
(설정하지 않는 경우 모든 IP와 port에서 접속 가능.)
# 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://[퍼블릭 IP]:9092
// =============== (3) ===============
카프카 클라이언트 또는 카프카 커맨드 라인 툴에서 접속할 때 사용하는 IP와 port 정보.
(인스턴스를 생성할 때 발급받은 퍼블릭 IPv4값을 IP에 넣고, port에는 카프카 기본 포트인 9092.)
# 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
// =============== (4) ===============
SASL_SSL,SASL_PLAIN 보안 설정 시 프로토콜 매핑을 위한 설정.
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3
// =============== (5) ===============
네트워크를 통한 처리를 할 때 사용할 네트워크 스레드 개수 설정이다. 1,1 Top
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8
// =============== (6) ===============
카프카 브로커 내부에서 사용할 스레드 개수.
# 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
// =============== (7) ===============
통신을 통해 가져온 데이터를 파일로 저장할 디렉토리 위치.
(디렉토리가 없는 경우 오류가 발생할 수 있으므로 브로커 실행 전에 디렉토리 생성 여부를 확인한다.)
# 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
// =============== (8) ===============
파티션 개수를 명시하지 않고 토픽을 생성할 때 기본 설정되는 파티션 개수.
(파티션 개수가 많아지면 병렬처리 데이터양이 늘어난다.)
# 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
// =============== (9) ===============
카프카 브로커가 저장한 파일이 삭제되기까지 걸리는 시간을 설정.
가장 작은 단위를 기준으로 하므로 log.retention.hours보다는 log.retention.ms 값을 설정하여
운영하는 것을 추천. log.rentention.ms 값을 -1로 설정하는 경우 삭제는 이루어지지 않는다.
# 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
// =============== (10) ===============
카프카 브로커가 저장할 파일의 최대 크기를 지정. (이 크기를 채운 경우 새로운 파일 생성.)
# 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
// =============== (11) ===============
카프카 브로커가 저장한 파일을 삭제하기 위해 체크하는 간격 지정.
############################# 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={host ip를 입력}:2181
// =============== (12) ===============
카프카 브로커와 연동할 주키퍼의 IP와 port를 설정.
실습을 위해 EC2 인스턴스에 주키퍼와 카프카 브로커를 동시에 실행하므로
host ip:2181로 설정한다.
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=18000
// =============== (13) ===============
주키퍼의 세션 타임아웃 시간을 지정. 121,1 89%
76,1 44%
############################# 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개이상의 서버로 구성한다.
1대만 실행하는 주키퍼를 'Qucik-and-dirty single-node'라 칭한다. (테스트용으로만 사용)
$ bin/zookeeper-server-start.sh -daemon config/zookeeper.properties
$ jps -vm
// 이상이 있는 경우 daemon을 제거. 로그를 확인하자.
// jps : JVM 프로세스 상태를 보는 도구.카프카 브로커 실행 및 로그 확인
$ bin/kafka-server-start.sh -daemon config/server.properties
$ jps -m
$ tail -f logs/server.log로컬 컴퓨터에서 카프카와 통신 확인
$ curl https://archive.apache.org/dist/kafka/2.5.0/kafka_2.12-2.5.0.tgz --output kafka.tgz
$ tar -xvf kafka.tgz
$ cd kafka_2.12-2.5.0
$ bin/kafka-broker-api-versions.sh --bootstrap-server [퍼블릭 IP]:9092테스트 편의를 위한 hosts 설정
$ vi /etc/hosts
[IP] my-kafkaLast updated