Resolution:
Description:
===========
Some best practices details while doing space recovery in ActiveSpaces

Environment:
===========
AS 2.*.*
All operating systems


Cause:
======
Sometimes if users recover space from as-admin without starting a minimum number of as-agent / SEEDER will cause data lose.

Resolution:
===========
- Proper replication degree will make sure tuple is stored in backup.
     Example. If data is critical to the user and they are running with 3 as-agent (SEEDERs) then the user can give the replication count as 2.

-  While doing recovery from as-admin, first we need to check if all the required seeders have joined a cluster or not. Provide some time to join all the seeder. Later the user can execute the recovery command from admin.

-  While running recovery the user can set the “Quorum”. Quorum is defined to be a minimum number of seeders in space for recovery to initiate. If metaspace is running with 32 Seeders, give quorum as 32 so that recovery won’t start until all the seeders are up.

User can set RecoveryOptions using the following methods from the API.

    /**
     * Set quorum size for recovery to start.
     *
     * @param seederCount Quorum is defined to be minimum number of seeders in space for recovery to initiate
     *
     * @return RecoveryOptions
     */
    RecoveryOptions setQuorum(int seederCount);

    /**
     * @return int quorum
     */
    int getQuorum ();

User can set “Quorum” from as-admin.

    recover space &ltname> with data quorum &ltnumber>
    recover space &ltname> without data quorum &ltnumber>

The default quorum is 1.

Hits for spaces recovery in ActiveSpaces when shared-nothing persistence is used.