In testing our 0.8 cluster, we started by just using the sample server.properties file that ships with 0.8 and tweaking it. The replication factor property did not have an exemplar in the file, so we didn't include it. Naturally, the cluster did not do replication.
After sending some data through the tests, we then added replication factor=2 to the config and restarted the cluster. After a half-hour it did not appear to replicate the topic data we had generated during the first test. We had to erase the topics entirely and start from scratch. Replication then happened and when we took down a broker we saw the gaps in the topic data get filled in after restarting it.
In the future, what is the correct way to get a Kafka cluster to change the replication factor on an existing topic? Will we have to flush all data from the cluster for a given topic, or is there a recommended way to convert existing data?
We do plan to support changing replication factors online in the future. This will be a post 0.8 feature though.
On Mon, Feb 11, 2013 at 9:32 AM, Bob Jervis <[EMAIL PROTECTED]
Jun Rao 2013-02-12, 05:42
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext