Error sending msg to Kafka topi

[MAHA ALSAYASNEH <ma...@univ-grenoble-alpes.fr>]

Hello, 

I always get this error when I send a big amount of data to the topic: 
"org.apache.kafka.common.errors.TimeoutException: Expiring 35 record(s) for words-4 due to 30006 ms has passed since batch creation plus linger time" 

If anybody faced that problem before, could you please share your solution? 

Thanks 
Maha 

Re: Error sending msg to Kafka topi

[MAHA ALSAYASNEH <ma...@univ-grenoble-alpes.fr>]

Here is my broker configuration: 

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

# The id of the broker. This must be set to a unique integer for each broker. 
broker.id=1 
host.name=xxxx 
port=9092 


#The maximum size of message that the server can receive 
message.max.bytes=2000024 


replica.fetch.max.bytes=2000024 
request.timeout.ms=300000 


# Switch to enable topic deletion or not, default value is false 
delete.topic.enable=true 

############################# 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 = security_protocol://host_name:port 
# EXAMPLE: 
# listeners = PLAINTEXT://your.host.name:9092 
listeners=PLAINTEXT://xxxx: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=PLAINTEXT://your.host.name:9092 

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

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

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

# 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=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 
# You can also append an optional chroot string to the urls to specify the 
# root directory for all kafka znodes. 
zookeeper.connect=xxxxxx:2181,xxxx:2181 

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


# metrics reporter properties 
kafka.metrics.polling.interval.secs=5 
kafka.metrics.reporters=kafka.metrics.KafkaCSVMetricsReporter 
kafka.csv.metrics.dir=/tmp/kafka_metrics 
# Disable csv reporting by default. 
kafka.csv.metrics.reporter.enabled=true 


######################################"" 


Thanks in advance! 

From: "MAHA ALSAYASNEH" <ma...@univ-grenoble-alpes.fr> 
To: "users" <us...@kafka.apache.org> 
Sent: Tuesday, September 26, 2017 11:07:07 AM 
Subject: Error sending msg to Kafka topi 

Hello, 

I always get this error when I send a big amount of data to the topic: 
"org.apache.kafka.common.errors.TimeoutException: Expiring 35 record(s) for words-4 due to 30006 ms has passed since batch creation plus linger time" 

If anybody faced that problem before, could you please share your solution? 

Thanks 
Maha