(all-topic-partitions zk-utils)
Returns all partitions for all topics.
Returns all partitions for all topics.
(isr-change-notification-path)
(partition-epoch zk-utils {:keys [topic partition]})
(partition-epoch zk-utils topic partition)
Returns the topic epoch from the ISR path in Zookeeper.
Returns the topic epoch from the ISR path in Zookeeper.
(partition-in-sync-replicas zk-utils {:keys [topic partition]})
(partition-in-sync-replicas zk-utils topic partition)
Returns the in-sync replicas for a topic partition.
Returns the in-sync replicas for a topic partition.
(partition-leader zk-utils {:keys [topic partition]})
(partition-leader zk-utils topic partition)
Returns the partition leader (if any) for a topic partition.
There may be no leader if one is not elected yet, in which case nil is returned.
Returns the partition leader (if any) for a topic partition. There may be no leader if one is not elected yet, in which case nil is returned.
(partition-leader-metadata zk-utils {:keys [topic partition]})
(partition-leader-metadata zk-utils topic partition)
Returns the partition leader (if any), a list of in-sync-replicas, and other metadata for a topic partition.
Returns the partition leader (if any), a list of in-sync-replicas, and other metadata for a topic partition.
(partition-leaders-for zk-utils topics)
Retrives the leaders (if any) for each partition in a given list of topics.
Each topic name will be the key in the returned map. Each topic may have multiple partitions, and each partition will have a list of partition leaders.
Example Output:
{:taco-bars {2 [1001], 1 [0], 0 [1001]}, :fajita-facts {2 [1001], 1 [1002], 0 [1001]}}
Retrives the leaders (if any) for each partition in a given list of topics. Each topic name will be the key in the returned map. Each topic may have multiple partitions, and each partition will have a list of partition leaders. Example Output: `{:taco-bars {2 [1001], 1 [0], 0 [1001]}, :fajita-facts {2 [1001], 1 [1002], 0 [1001]}}`
(partition-leaders-metadata zk-utils topic-partitions)
(partition-replica-assignment zk-utils {:keys [topic partition]})
(partition-replica-assignment zk-utils topic partition)
Returns the assigned replicas for a given topic and partition.
Returns a vector of assigned replica IDs
Example:
[1001 1002]
Returns the assigned replicas for a given topic and partition. Returns a vector of assigned replica IDs Example: `[1001 1002]`
(partitions-for zk-utils topics)
Returns all partitions for each topic, given a collection of topic names.
Returns all partitions for each topic, given a collection of topic names.
(partitions-undergoing-reassignment zk-utils)
(partitions-undergoing-replica-election zk-utils)
Returns partitions undergoing preferred replica election.
Returns partitions undergoing preferred replica election.
(reassign-partitions-path)
(redefine-partition-count! zk-utils topic partitions)
(redefine-partition-count! zk-utils
topic
partitions
replica-assignment
check-broker-available?)
(redefine-partition-count! zk-utils
topic
partitions
replica-assignment
check-broker-available?
rack-aware-mode)
Sets the number of partitions for a topic, given the topic, number of partitions, replica assignment, and a flag to check if the broker is available before attempting to redefine the count.
Note that the number of partitions for a topic can only be increased without first deleting partitions. For example, if you have 5 partitions for a given topic, you can set the number of partitions to 10, but not to 5, 4, 3, etc...
Please be sure you know what you are doing when you repartitioning a topic. Repartitoning may result in unintended consequences regarding your key ordering. If you are not concerned about ordering, have not added data to your topic yet, or otherwise can deal with ordering issues via replay or in your application itself, then you may use this method to increase the amount of partitions for your topic.
An AdminOperationException will be thrown if you attempt to redefine an invalid number of partitions.
Note: This method may be changed/depricated given the state of this API in the official Kafka branch.
Sets the number of partitions for a topic, given the topic, number of partitions, replica assignment, and a flag to check if the broker is available before attempting to redefine the count. Note that the number of partitions for a topic can only be increased without first deleting partitions. For example, if you have 5 partitions for a given topic, you can set the number of partitions to 10, but not to 5, 4, 3, etc... Please be sure you know what you are doing when you repartitioning a topic. Repartitoning may result in unintended consequences regarding your key ordering. If you are not concerned about ordering, have not added data to your topic yet, or otherwise can deal with ordering issues via replay or in your application itself, then you may use this method to increase the amount of partitions for your topic. An AdminOperationException will be thrown if you attempt to redefine an invalid number of partitions. > Note: This method may be changed/depricated given the state of this API in the official Kafka branch.
(replica-leader-election-path)
(topic-partition-isr-leader-path topic partition)
Returns the topic partition leader and in-sync replica path in Zookeeper.
Returns the topic partition leader and in-sync replica path in Zookeeper.
(topic-partition-path topic partition)
Returns the Zookeeper topic partition path.
Returns the Zookeeper topic partition path.
(topic-partitions-path topic)
Returns the path for partitions for a given topic in Zookeeper.
Returns the path for partitions for a given topic in Zookeeper.
(write-topic-partition-assignment-path! zk-utils
topic
partition-replica-assignment
config
update?)
Given a topic and map of partition replica assignments, creates or updates the partition assignment path with a given config.
Given a topic and map of partition replica assignments, creates or updates the partition assignment path with a given config.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close