Managing a Development or Test Environment

If you have a test or a development environment where you are creating, using and then destroying multiple grids, you may need to purge the membership service metadata for any grid that is destroyed and will not be used again.

TimesTen Scaleout creates membership service metadata to represent each independent grid on each instance in a grid. If you know that a particular grid has been destroyed and is never going to be used again, then you can perform the following on one instance:

Locate the timesten.conf configuration file in the /conf directory under the instance home directory.
Identify the membership service entries in the timesten.conf configuration file with the grid_guid and grid_name parameters, such as:
```
grid_guid=4012FC64-8B9X-45D1-A16C-ED52C3098CAD
grid_name=grid1
```
The membership service entry has the naming structure of grid_name.grid_guid and exists within the /oracle/timesten/grid/membership directory.

Note:

It is imperative that you identify the correct grid to avoid deleting a membership service of an active grid.
Run the zkCli.sh command to connect to the membership servers.
```
% ./zkCli.sh -server ms_host1:2181
```

Using the zkCli.sh rmr command, delete the membership service entries.

rmr /oracle/timesten/grid/membership/grid1.4012FC64-8B9B-45D1-A16C-ED52C3098CAD