Description:
When you want to drop a space from admin CLI, it seems that you have to stop all members of the space. Currently we use the as-agent process as seeder processes and they are managing the metaspace. However this also stops the other spaces in the same metaspace to be available for leeches and we have to recover them after starting the metaspace. What is the best approach to drop a space of an existing metaspace without impacting other spaces? Keep a 1-on-1 relationship between metaspace and space?

What is the best approach to drop a space of an existing metaspace without impacting other spaces?

One option with the new version of the as-admin tool (starting with 2.1.2HF9 and above) is the ability to execute admin commands from as-admin on other metaspace member processes. One of the new commands you can execute remotely is 'leave space'.

So if you want to drop a space called "myspace" while as-agents are running you could run the following from the admin tool:

execute on members leave space "myspace"

This will mean all metaspace members will leave the space. An error may be thrown from some of the metaspace members if they were not joined to the space.You can then verify that there are no more members to the space doing a "show space "myspace"". The space can be defined again and the as-agents will automatically re-join the newly re-defined space.

You may not want to keep a 1-to-1 relationship between spaces and metaspaces, To draw a parallel with databases think of the Metaspace as your database instance, the spaces as tables, and the tuples as rows. you also have to do 'drop space' after all members have left it before you can re-define it with a different definition.

Refer AS 2.1.2 HF-09 addendum