Ansible部署系列续：（二）安装Kafka

2. 安装Kafka

2.1. 说明

由于之前的项目用到Kafka，在这里也记录一下。
ansiblehosts文件，broker_id从0开始

[kafkaservers]
sz-1 broker_id=0
sz-2 broker_id=1

vars.yml添加参数

KAFKA_DATA_DIR: /home/data/kafka
KAFKA_PARTITIONS: 2
KAFKA_SASL_PLAINTEXT: SASL_PLAINTEXT
KAFKA_PLAINTEXT: PLAINTEXT

2.2. yml脚本

---
- hosts: kafkaservers
  remote_user: root
  vars_files:
    - ../vars.yml

  tasks:
    - name: copy and unzip kafka
      unarchive:
        src: "{{ PLAYBOOK_DIR }}/files/kafka_2.12-2.5.0.tgz"
        dest: "{{ INSTALL_DIR }}"

    - name: mkdir ditectory for kafka data
      file:
        dest: "{{ KAFKA_DATA_DIR }}"
        mode: 0755
        state: directory
        owner: root
        group: root

    - name: install properties file for kafka
      template:
        src: "{{ PLAYBOOK_DIR }}/kafka/templates/server.properties.j2"
        dest: "{{ INSTALL_DIR }}/kafka_2.12-2.5.0/config/server.properties"
        owner: root
        group: root
        mode: 0755

    # - name: set login config
    #   lineinfile:
    #     dest: "{{ INSTALL_DIR }}/kafka_2.12-2.5.0/bin/kafka-server-start.sh"
    #     insertafter: "{{ item.position }}"
    #     line: "{{ item.value }}"
    #     state: present
    #   with_items:
    #     - { position: EOF, value: '#export KAFKA_OPTS="-Djava.security.auth.login.config=/opt/kafka_2.12-2.5.0/config/kafka-server-jaas.conf"' }
    - name: copy kafka jaas config
      template:
        src: "{{ PLAYBOOK_DIR }}/kafka/templates/kafka-server-jaas.conf"
        dest: "{{ INSTALL_DIR }}/kafka_2.12-2.5.0/config/kafka-server-jaas.conf"
        owner: root
        group: root
        mode: 0755

    - name: copy zk jaas config
      template:
        src: "{{ PLAYBOOK_DIR }}/kafka/templates/kafka-zk-jaas.conf"
        dest: "{{ INSTALL_DIR }}/kafka_2.12-2.5.0/config/kafka-zk-jaas.conf"
        owner: root
        group: root
        mode: 0755

    - name: set sysctl.conf #设置
      lineinfile:
        dest: /etc/sysctl.conf
        insertafter: "{{ item.position }}"
        line: "{{ item.value }}"
        state: present
      with_items:
      - { position: EOF, value: "vm.max_map_count=1048575" }

    - name: restart config  #刷新
      shell: sysctl -p

    - name: firewarld add 9092
      firewalld:
        port: 9092/tcp
        permanent: true
        immediate: true
        zone: public
        state: enabled

    - name: firewarld add 2181
      firewalld:
        port: 2181/tcp
        permanent: true
        immediate: true
        zone: public
        state: enabled

    - name: copy start.sh
      template:
        src: "{{ PLAYBOOK_DIR }}/kafka/templates/start.sh.j2"
        dest: "{{ INSTALL_DIR }}/kafka_2.12-2.5.0/bin/start.sh"
        owner: root
        group: root
        mode: 0755
        
      tags:
        - start kafka

自己写了个脚本进行启动，但ansible启动不成功，只好自己去每个节点进行命令启动，原因至今无解。已弃Kafka，转RabbitMQ。
set login config设置是为了建立安全连接，后面觉得太麻烦，不用密码了，所以注释掉了。
jass config也是一样，只是拷贝过去，以备不时之需。

1.3. 模板文件

因为搭建的是集群环境，因此都需要配置节点

1.3.1 server.properties.j2

# 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={{ broker_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://{{ ansible_default_ipv4.address }}:9092
# listeners={{ KAFKA_SASL_PLAINTEXT }}://{{ inventory_hostname }}:9092

# 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={{ KAFKA_PLAINTEXT }}://{{ inventory_hostname }}: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

# 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={{ KAFKA_DATA_DIR }}

# 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={{ KAFKA_PARTITIONS }}

# 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

# 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={% set comma = joiner(",") %}
{% for item in groups['kafkaservers'] -%}
    {{ comma() }}{{ hostvars[item].inventory_hostname }}:2181
{%- endfor %}

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=60000


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


#security.inter.broker.protocol={{ KAFKA_SASL_PLAINTEXT }}
#sasl.enabled.mechanisms=PLAIN
#sasl.mechanism.inter.broker.protocol=KAFKA_PLAIN
#authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
#super.users=User:admin

1.3.2 kafka-server-jaas.conf

具体含义是啥忘记了

KafkaServer {
        org.apache.kafka.common.security.plain.PlainLoginModule required
        username="admin"
        password="123456"
        user_admin="123456"
        user_another="anson";
};

1.3.3 kafka-zk-jaas.conf

具体含义是啥忘记了

zookeeper {
        org.apache.kafka.common.security.plain.PlainLoginModule required
        username="admin"
        password="123456";
};

1.3.3 start.sh.j2

启动脚本

#!/bin/bash
ulimit -n 65535
JMX_PORT=9093 {{ INSTALL_DIR }}/kafka_2.12-2.5.0/bin/kafka-server-start.sh -daemon {{ INSTALL_DIR }}/kafka_2.12-2.5.0/config/server.properties

1.4. 运行ansible-playbook

ansible-playbook -i /etc/ansible/hosts kafka/main.yml

1.5. 基本命令

新建topic，生产者发送消息，消费者消费消息

/opt/kafka_2.12-2.5.0/bin/kafka-topics.sh --create --bootstrap-server 192.168.11.138:9092 --replication-factor 2 --partitions 2 --topic test
/opt/kafka_2.12-2.5.0/bin/kafka-console-producer.sh --bootstrap-server 192.168.0.235:9092 --topic test
/opt/kafka_2.12-2.5.0/bin/kafka-console-consumer.sh --bootstrap-server 192.168.0.236:9092 --topic test --from-beginning