NCL Community Forum Index
  Home   Login   Register   Help   Memberlist   Search   NCL  

NCL Community Forum Index » Provato Support » Cluster Configuration for Provato 1.4
Post new topic  Reply to topic View previous topic :: View next topic 
Cluster Configuration for Provato 1.4
PostPosted: Thu May 06, 2010 10:45 am Reply with quote
Administrator
Site Admin
Joined: 11 Aug 2004
Posts: 237




Provato 1.4 clustered instances run independent of each other.

Message locking is performed at database level so that multiple nodes do not deliver the same message more than once. Messages are locked but the locks expire so in the event of a node failure, another node will pickup the locked messages after the locks expire.

Each instance of Provato running in a cluster requires a unique name. This name is used to lock messages in the message table. Provato needs to also be configured to run in message locking mode.

The cluster configuration is stored in a file called Cluster.properties that is different for each node in the cluster. This file is stored in the same directory as the Licens.properties file (location varies depending on build). A sample Cluster.properties file is
Code:

node.names=Node1 Node2 ...
node.useMessageLocking=true
container.name=Node1



Note that in this clustering mode, Provato uses a differnt table for storing messages. The table is called PROVATO_MESSAGES_CLUSTER with the format:
Code:

create table PROVATO_MESSAGES_CLUSTER
  (id varchar(40) not null,
  queueName varchar(128) not null,
  schedule timestamp not null,
  messagedata blob,
  lockedBy varchar(40),
  lockUntil timestamp,
  primary key(id) )


In non-clustered mode the table used for storing messages is PROVATO_MESSAGES
Code:

create table PROVATO_MESSAGES \
  (id varchar(40) not null,
  queueName varchar(128) not null,
  schedule timestamp not null,
  messagedata blob,
  primary key(id) )


Migrating
Note that when migrating from a clustered mode from a standalone mode, messages in the old table (either retried or undelivered) will no longer be processed. If you require these messages then you will need to copy them in from the old PROVATO_MESSAGES table to the new PROVATO_MESSAGES_CLUSTER table using your database SQL.

Starting Provato 1.4 in clustered mode automatically creates the table.
View user's profile Send private message

Cluster Configuration for Provato 1.4
 NCL Community Forum Index » Provato Support
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT  
Page 1 of 1  

  
  
 Post new topic  Reply to topic