My topic has 3 partitions (in 3 different brokers). I want to send message to particular partition 1 (add partition id or specify a key in my message). Assuming the partition 1 became full of disk, does an alternative partition (partition 2 or 3 in this case) be chosen for this message?
Does Kafka chose an alternative partition in the same topic if the partition I want to send message to was full of disk?
143 Views Asked by Hieu Doan At
1
There are 1 best solutions below
Related Questions in APACHE-KAFKA
- Spark streaming + kafka throughput
- How to diagnose Kafka topics failing globally to be found
- kafka: what do 'soTimeout', 'bufferSize' and 'minBytes' mean for SimpleConsumer?
- Fail to create SparkContext
- Syntax error on tokens, delete these tokens - kafka spring integration demo application
- How could Kafka 0.8.2.1 with offsets.storage=kafka still require ZooKeeper?
- Message Queues: Per Message Guarantees
- How should a Kafka HLC figure out the # of partitions for a topic?
- Kafka multiple consumers for a partition
- Should Apache Kafka and Hadoop be installed seperatedly (on a diffrent cluster)?
- how does one combine kafka-node producer and node tail?
- How to fix NoClassDefFoundError with custom Kafka producer under Eclipse?
- Apache Samza's CheckpointTool won't give away partition offsets
- Offsets for Kafka Direct Approach in Spark 1.3.1
- Simulate kafka broker failures in multi node kafka cluster and what operations and tools to use to mitigate data loss issues
Related Questions in KAFKA-TOPIC
- How Kafka guarantee the messages order while we increase the partitions in runtime?
- Apache Flink - Partitioning the stream equally as the input Kafka topic
- Does Kafka chose an alternative partition in the same topic if the partition I want to send message to was full of disk?
- What happens to the offsets that are compacted in a kafka partition?
- Does Kafka consumer reads the message from active segment in the partition?
- after kafkaTemplate.send(topic, avdlObject); appends dataType in value
- In Kafka, the topic is not getting leader after recreation post deletion
- How to send headers from Pentaho DI to Kafka?
- How to access Kafka through nodeport
- Can compacted Kafka topic be used as key-value database?
- Kafka topic returns 0 messages
- Where is offset of consumer stored in Kafka
- Kafka: auto create topic with options
- Decrease topic replication factor after Kafka brokers removed from cluster and failed reassignments
- How to programmatically create a topic in Apache Kafka using C++ client librdkafka
Related Questions in KAFKA-PARTITION
- How Kafka guarantee the messages order while we increase the partitions in runtime?
- Does Kafka chose an alternative partition in the same topic if the partition I want to send message to was full of disk?
- What happens to the offsets that are compacted in a kafka partition?
- Does Kafka consumer reads the message from active segment in the partition?
- Consuming kafka batch for multiple partitions
- My Kafka Topic has three partitions. I cyclic read from all partitions the newest data coming from source, but one reading cycle takes too long. Why?
- Decrease topic replication factor after Kafka brokers removed from cluster and failed reassignments
- Does Kafka Streams GlobalKTable topic require the same number of partitions as KStream topic which it will be joining with?
- Properly Seek and Consume Kafka Messages on Multipartition Topic
- Spring boot kafka: Microservice multi instances, concurrency and partitions
- Size of Kafka Partitions and writing to a Topic with no free disk space
- Kafka is not sending messages to other partitions
- why Kafka consumer group is doing a partition revoking for different topics?
- Use kafka partitioner as a lock
- Do Kafka's parallelism concepts apply when running in console mode?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
It is not the topic that is running out of disk but only the entire broker. If the broker runs out of disk it will shut itself down and you will not be able to send to or receive data from it.
As you are specifically pointing to a partition, it now depends if you have a replication-factor value larger than 1. In case you have replicated your topic partitions, the partition leader would switch from the dead broker to another broker with that has a partition in-sync.
If you do not have replication of more than 1 your producer would end up getting an OutOfMemory error and the data it not produced to the alternative partitions 2 or 3.
To make sure that this never happens you can apply the volume based retention policies that is available in Kafka if you set your
cleanup.policyto delete and set theretention.bytessuch that with the number of topics/replicas you will not exceed your storage limit.