login as: ec2-user
Authenticating with public key "imported-openssh-key"
Last login: Wed Apr 27 09:03:50 2016 from 80.93.235.42

       __|  __|_  )
       _|  (     /   Amazon Linux AMI
      ___|\___|___|

https://aws.amazon.com/amazon-linux-ami/2016.03-release-notes/
No packages needed for security; 5 packages available
Run "sudo yum update" to apply all updates.
[ec2-user@ip-172-31-27-189 ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      7.8G  3.5G  4.3G  45% /
devtmpfs        3.9G   68K  3.9G   1% /dev
tmpfs           3.9G     0  3.9G   0% /dev/shm
/dev/xvdf       788G  213G  535G  29% /mnt/ephemeral
[ec2-user@ip-172-31-27-189 ~]$ cd /mnt/ephemeral/log/
jetty/ kafka/
[ec2-user@ip-172-31-27-189 ~]$ cd /mnt/ephemeral/log/
jetty/ kafka/
[ec2-user@ip-172-31-27-189 ~]$ cd /mnt/ephemeral/log/kafka/
[ec2-user@ip-172-31-27-189 kafka]$ ls
broker_logs                   kafka-startup.log
controller.log                log-cleaner.log
controller.log.2016-04-22-23  server.log
controller.log.2016-04-23-00  server.log.2016-04-22-23
controller.log.2016-04-23-01  server.log.2016-04-23-00
controller.log.2016-04-23-02  server.log.2016-04-23-01
controller.log.2016-04-23-03  server.log.2016-04-23-02
controller.log.2016-04-23-04  server.log.2016-04-23-03
controller.log.2016-04-23-05  server.log.2016-04-23-04
controller.log.2016-04-23-06  server.log.2016-04-23-05
controller.log.2016-04-23-07  server.log.2016-04-23-06
controller.log.2016-04-23-08  server.log.2016-04-23-07
controller.log.2016-04-23-09  server.log.2016-04-23-08
controller.log.2016-04-23-10  server.log.2016-04-23-09
controller.log.2016-04-23-11  server.log.2016-04-23-10
controller.log.2016-04-23-12  server.log.2016-04-23-11
controller.log.2016-04-23-13  server.log.2016-04-23-12
controller.log.2016-04-23-14  server.log.2016-04-23-13
controller.log.2016-04-23-15  server.log.2016-04-23-14
controller.log.2016-04-23-16  server.log.2016-04-23-15
controller.log.2016-04-23-17  server.log.2016-04-23-16
controller.log.2016-04-23-18  server.log.2016-04-23-17
controller.log.2016-04-23-19  server.log.2016-04-23-18
controller.log.2016-04-23-20  server.log.2016-04-23-19
controller.log.2016-04-23-21  server.log.2016-04-23-20
controller.log.2016-04-23-22  server.log.2016-04-23-21
controller.log.2016-04-23-23  server.log.2016-04-23-22
controller.log.2016-04-24-00  server.log.2016-04-23-23
controller.log.2016-04-24-01  server.log.2016-04-24-00
controller.log.2016-04-24-02  server.log.2016-04-24-01
controller.log.2016-04-24-03  server.log.2016-04-24-02
controller.log.2016-04-24-04  server.log.2016-04-24-03
controller.log.2016-04-24-05  server.log.2016-04-24-04
controller.log.2016-04-24-06  server.log.2016-04-24-05
controller.log.2016-04-24-07  server.log.2016-04-24-06
controller.log.2016-04-24-08  server.log.2016-04-24-07
controller.log.2016-04-24-09  server.log.2016-04-24-08
controller.log.2016-04-24-10  server.log.2016-04-24-09
controller.log.2016-04-24-11  server.log.2016-04-24-10
controller.log.2016-04-24-12  server.log.2016-04-24-11
controller.log.2016-04-24-13  server.log.2016-04-24-12
controller.log.2016-04-24-14  server.log.2016-04-24-13
controller.log.2016-04-24-15  server.log.2016-04-24-14
controller.log.2016-04-24-16  server.log.2016-04-24-15
controller.log.2016-04-24-17  server.log.2016-04-24-16
controller.log.2016-04-24-18  server.log.2016-04-24-17
controller.log.2016-04-24-19  server.log.2016-04-24-18
controller.log.2016-04-24-20  server.log.2016-04-24-19
controller.log.2016-04-24-21  server.log.2016-04-24-20
controller.log.2016-04-24-22  server.log.2016-04-24-21
controller.log.2016-04-24-23  server.log.2016-04-24-22
controller.log.2016-04-25-00  server.log.2016-04-24-23
controller.log.2016-04-25-01  server.log.2016-04-25-00
controller.log.2016-04-25-02  server.log.2016-04-25-01
controller.log.2016-04-25-03  server.log.2016-04-25-02
controller.log.2016-04-25-04  server.log.2016-04-25-03
controller.log.2016-04-25-05  server.log.2016-04-25-04
controller.log.2016-04-25-06  server.log.2016-04-25-05
controller.log.2016-04-25-07  server.log.2016-04-25-06
controller.log.2016-04-25-08  server.log.2016-04-25-07
controller.log.2016-04-25-09  server.log.2016-04-25-08
controller.log.2016-04-25-10  server.log.2016-04-25-09
controller.log.2016-04-25-11  server.log.2016-04-25-10
controller.log.2016-04-25-12  server.log.2016-04-25-11
controller.log.2016-04-25-13  server.log.2016-04-25-12
controller.log.2016-04-25-14  server.log.2016-04-25-13
controller.log.2016-04-25-15  server.log.2016-04-25-14
controller.log.2016-04-25-16  server.log.2016-04-25-15
controller.log.2016-04-25-17  server.log.2016-04-25-16
controller.log.2016-04-25-18  server.log.2016-04-25-17
controller.log.2016-04-25-19  server.log.2016-04-25-18
controller.log.2016-04-25-20  server.log.2016-04-25-19
controller.log.2016-04-25-21  server.log.2016-04-25-20
controller.log.2016-04-25-22  server.log.2016-04-25-21
controller.log.2016-04-25-23  server.log.2016-04-25-22
controller.log.2016-04-26-00  server.log.2016-04-25-23
controller.log.2016-04-26-01  server.log.2016-04-26-00
controller.log.2016-04-26-02  server.log.2016-04-26-01
controller.log.2016-04-26-03  server.log.2016-04-26-02
# 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=1

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

listeners=PLAINTEXT://:9092

# The port the socket server listens on
port=9092

# Hostname the broker will bind to. If not set, the server will bind to all interfaces
host.name=172.31.27.20

# Hostname the broker will advertise to producers and consumers. If not set, it uses the
# value for "host.name" if configured.  Otherwise, it will use the value returned from
# java.net.InetAddress.getCanonicalHostName().
advertised.host.name=172.31.27.20

# The port to publish to ZooKeeper for clients to use. If this is not set,
# it will publish the same port that the broker binds to.
#advertised.port=<port accessible by clients>

# The number of threads handling network requests
num.network.threads=3

# The number of threads doing 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 seperated list of directories under which to store log files
log.dirs=/mnt/ephemeral/log/kafka/broker_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=20

# 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

############################# 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 exceessive 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
log.retention.hours=48

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining
# segments don't drop below log.retention.bytes.
#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=536870912

# 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

# By default the log cleaner is disabled and the log retention policy will default to just delete segments after their retention expires.
# If log.cleaner.enable=true is set the cleaner will be enabled and individual logs can then be marked for log compaction.
log.cleaner.enable=false

############################# 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. "172.31.27.20:3000,172.31.27.20:3001,172.31.27.20:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
zookeeper.connect=172.31.46.218:2181,172.31.18.247:2181,172.31.9.232:2181

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

#metric.reporters=org.apache.kafka.common.metrics.JmxReporter

# Default Replication Factor for Automatically Created Topics
default.replication.factor=2