1.0

Table Of Contents

When you restart the servers, you may notice messages similar to:

[info 2012/07/24 10:18:11.949 PDT <main> tid=0x1] Region

/_DDL_STMTS_META_REGION initialized with data from

/10.118.33.206:/Users/yozie/vFabric_SQLFire_103/server1/./datadictionary

created at timestamp 1343149012698 version 0 diskStoreId

1fc6a853-69d6-4ffe-8029-218acf165c34 is waiting for the data previously

hosted at

[/10.118.33.206:/Users/yozie/vFabric_SQLFire_103/server2/./datadictionary

created at timestamp 1343149035681 version 0 diskStoreId

49c1e827-4bb5-49cc-951b-221d47bbc92f] to be available

These are not error messages. They indicate that the SQLFire member you are starting is waiting for another

member to become available online.

6. Now verify that the persistent tables were reloaded:

sqlf

connect client 'ip_address:1527';

select id from sys.systables s, sys.members where s.tablename='FLIGHTS';

select count(*) memberRowCount, dsid() from flights group by dsid();

Add Servers to the Cluster and Stop Servers

SQLFire manages data in a ﬂexible way that enables you to expand or contract your cluster at runtime to support

different loads. To dynamically add more capacity to a cluster, you add new server members and specify the

-rebalance option.

Procedure

1. Open a new terminal or command prompt window, and create a directory for the new server. Also set your

PATH in the new terminal if necessary:

cd ~/vFabric_SQLFire_10x

mkdir server3

export PATH=$PATH:~/vFabric_SQLFire_10x/bin

Start the new server with a unique port number and specify the -rebalance option:

sqlf server start -dir=server3 -locators=ip_address[10101]

-client-bind-address=ip_address -client-port=1530 -rebalance &

3. View the contents of the new SQLFire directory:

ls server3

Notice that the new SQLFire server also persists the available table data, and contains the same disk store

ﬁles as the other two servers.

You can view all members of the distributed system using sqlf. In the available sqlf session, execute the

query:

select id from sys.members;

5. Verify that all servers now host the data:

select id from sys.systables s, sys.members where s.tablename='FLIGHTS';

6. Examine the table data that each server hosts:

select count(*) memberRowCount, dsid() from flights group by dsid();

Exit the sqlf session:

exit;

Tutorials