| Title: | MAILBUS - Message Router and its Gateways |
| Notice: | Kit Copy Utility - 100.1, Problems - 5.*, Kit Support - 103.1 |
| Moderator: | FORTY2::YUILLE |
| Created: | Thu Jun 11 1992 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3209 |
| Total number of notes: | 7125 |
A question regarding DDS.
If you have a 3 node DDS network, with all nodes World Search
nodes, and Nodea A as a Master node.
I am decommisioning Node C, and want therefore to get rid of the
entries owned by this node.
They have all been deleted on node C and do not show when you show the
subscribers. They do however, exist on the Nodes A and B. My
understanding, (however wrong), is that DDS$TIDY and DDS$REFRESH need
to be run on nodes A and B, to clear all the old addresses.
I have tried running these two jobs interactively without success,
as the procedure says that a PURGE cannot be performed until it its
next schedule. Is this normal behaviour, or am I likely to break
something ?
I am not comfortable about decommisioning the machine until I can be
sure that the updates have been accepted by Nodes A and B.
Many Thanks
Ivan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3204.1 | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Wed May 14 1997 13:31 | 13 | |
TIDY and REFRESH are not involved in the process you discuss.
Deleting the master copy of an object should generate transactions
to the WSnodes to remove the replica from their databases. If this
has not occurred I'd suspect a communication problem between NodeC
and the other two nodes.
BTW, all you really need to do to 'decommission' NodeC is to do a
MBMAN DEL DDS NODE NodeC on the DDS Master node. The master node will
inform the other nodes that NodeC is leaving the DDS network, and
each node will remove all objects owned by NodeC from it's database.
Dave
| |||||
| 3204.2 | Cache ? | KERNEL::BURDENI | Wed May 14 1997 15:56 | 7 | |
Thanks for the reply, but a couple of quick questions,
Does DDS$REFRESH remove entries from cache ?
Also, when you remove the node, does the DDS network then actively
remove all the entries, or are the updates pending ?
Ivan.
| |||||
| 3204.3 | ACISS2::LENNIG | Dave (N8JCX), MIG, @CYO | Wed May 14 1997 16:43 | 17 | |
If an entry in the cache has not been 'touched' in 42 days,
dds$refresh checks the cache entry against the master copy.
If the master copy does not exist, the cache entry is removed.
Cache entries are also removed on a least-recently-used basis
as new entries are cached.
Deleting a node generates a nodelist update transaction; this
transaction can be deferred (if the DDS config option is used).
When the update is processed, replication transactions are
generated and queued for transmission to the other nodes. When
a node processes a nodelist replication transaction, besides the
obvious step of updating the nodelist object in its database, it
checks for node(s) being deleted and if so, removes all objects
owned by the deleted node from its database. Note that the node
being deleted does not receive the replication transaction.
Dave
| |||||
| 3204.4 | Thanks | KERNEL::BURDENI | Wed May 14 1997 17:10 | 1 | |
Thanks again, I really was not sure (obviously) how this worked. | |||||