As containers come online and offline, the catalog service places shards on available containers based on the rules in the ObjectGrid deployment configuration file. After starting the catalog service, there are zero containers available for shard placement. Let's use the xsadmin
tool to find out how shards are placed as we add containers to the deployment. We'll change some of the settings in the ogdeployment.xml
file we used earlier. We will only change the number of partitions and replicas:
<?xml version="1.0" encoding="UTF-8"?> <deploymentPolicy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ibm.com/ws/objectgrid/deploymentPolicy ../deploymentPolicy.xsd" xmlns="http://ibm.com/ws/objectgrid/deploymentPolicy"> <objectgridDeployment objectgridName="PaymentProcessorGrid"> <mapSet name="ppMapSet" numberOfPartitions="11" minSyncReplicas="1" maxSyncReplicas="1" maxAsyncReplicas="1"> <map ref="Payment"/> <map...