Yes you can. You can use the partition-reassignment tool and move it to a
smaller number of replicas.
-Clark
Clark Elliott Haskins III
LinkedIn DDS Site Reliability Engineer
Kafka, Zookeeper, Samza SRE
Mobile: 505.385.1484
BlueJeans: https://www.bluejeans.com/chaskins
chask...@linkedin.com
http
On Thu, May 22, 2014 at 7:29 AM, Jun Rao wrote:
> That's exactly what partition reassignment does. It may take a bit of time
> for the reassignment to complete.
>
> For example, if you initiate the process to change the replica assignment
> from {1, 2, 3} to {4,5,6}, the values in the assigned re
That's exactly what partition reassignment does. It may take a bit of time
for the reassignment to complete.
For example, if you initiate the process to change the replica assignment
from {1, 2, 3} to {4,5,6}, the values in the assigned replica (AR) and
leader/isr path in ZK may go through the fol
On Wed, May 21, 2014 at 9:06 PM, Jun Rao wrote:
> Expansion can be done by following
> http://kafka.apache.org/documentation.html#basic_ops_cluster_expansion
>
> If you just want to free up a server, you can stop the broker there and
> start a broker using the same broker id on a new server. Data
Expansion can be done by following
http://kafka.apache.org/documentation.html#basic_ops_cluster_expansion
If you just want to free up a server, you can stop the broker there and
start a broker using the same broker id on a new server. Data should be
automatically replicated to the new server.
Tha
Any suggestions? I'm kind of in a bind in that I don't understand how to
grow the cluster when more capacity is needed--which happens to be right
now for me.
The only thing I can think that might work is to create new brokers,
cherry-pick topic/partition pairs and move them, then turn off the old
On Wed, May 21, 2014 at 9:11 AM, David Birdsong wrote:
> Here's the reassignment json and current "describe" output:
> https://gist.github.com/davidbirdsong/32cd0c4f49496a6a32e5
>
>
> In my re-assignment json, I tried to re-assign to 2 when the repl is set
> to 3. Once I noticed the the completely
Here's the reassignment json and current "describe" output:
https://gist.github.com/davidbirdsong/32cd0c4f49496a6a32e5
In my re-assignment json, I tried to re-assign to 2 when the repl is set to
3. Once I noticed the the completely new node "133" had appeared in the
ISR, I tried stopping 224, wip
During the re-assignment, did you move the replica off the old broker?
Thanks,
Jun
On Wed, May 21, 2014 at 8:21 AM, David Birdsong wrote:
> I did that and so now the topic has 4 replicas for a repl count of 3, but
> only the 'new' replicas exist in the ISR.
>
> The old broker that I want to cl
It is possible to do this using the kafka-reassign-partitions admin
command. You can explicitly set the replica list for a partition to be
less than the current replication factor, and that will effectively reduce
it. However, I will say that you should be really sure that you want to do
this. If,
I did that and so now the topic has 4 replicas for a repl count of 3, but
only the 'new' replicas exist in the ISR.
The old broker that I want to clear disk space and generally free up
resources has fully synced a topic that I want to disassociate from it.
Is there a way to do this?
On Wed, May
We don't have an exact tool for doing this. You may be able to do that
through
http://kafka.apache.org/documentation.html#basic_ops_increase_replication_factorby
specifying fewer replicas.
Thanks,
Jun
On Wed, May 21, 2014 at 1:23 AM, David Birdsong wrote:
> Is there a way to reduce the replica
Is there a way to reduce the replication count? I'm trying to spread
existing partitions across more brokers, but it's hard to decomm a broker.
Reducing repl count would suffice for now.
Any tips?
I'm running a mix of 0.8.1.1 and 0.8.1 (I'm upgrading now.)
13 matches
Mail list logo
