On Mon, Feb 13, 2017 at 10:15 PM, bjb <bjb2...@163.com> wrote: > Hi All: > I have two questions on understanding cluster-admin implemention: > > 1. cluster-admin:remove_shard_replica > This api is to remove the shard replica on particular member. There is > a variable in AbstractLeader.java named 'minReplicationCount' which does > not update when shard replica is removed. > Eg: 5 cluster members ecah have shard 'default', node 1 is leader. > After invoking the api to remove shard 'default' on member 4, 5, the > minReplicationCount is still 3. Why not recalculate the remain 3 member > whose minReplicationCount is actually 2? > > That is an oversight.
> 2. cluster-admin:backup-datastore > The implemention of GetSnapshot is to capture the snapshot for > persistent shard, and to initiate a snapshot containing just the > persistable(eg election term info) for non-persistent shard. > In some situation, I want to export the config-datastore(persistent) and > the operational-datastore(non-persistent) on production environment and > to restore them on testing environment to reproduce the running status. But > the non-persistent is not available using backup api. How can I export both > non-persistent and persistent datastore? > > The point of the backup is to backup persistent data since non-persistent operational data is reproduced on restart. > Hope to get your help. > Thanks > > > > > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
