Open topic with navigation

TIBCO Rendezvous® 8.7.0

# TOO_MANY_ACTIVE

Advisory

## Subject Name Syntax

    _RV.WARN.RVFT.TOO_MANY_ACTIVE.group

## Purpose

A fault tolerance member presents this warning advisory message when it detects that too many group members are active. This situation is usually transient, and resolves itself quickly without intervention. However, if the situation persists, it might indicate problems that require attention.

## Remarks

Rendezvous fault tolerance software detects the situation when it receives a heartbeat message from a member that was not already known to be active.

This warning indicates that the following conditions all hold simultaneously:

| • | The number of members broadcasting heartbeat messages is greater than the active goal parameter.

| • | This member is active.

| • | This member will not deactivate (that is, its rank indicates it should remain active).

The conclusion is that one or more other members are active that should not be active. In most cases those members quickly detect the anomaly, and deactivate. Normally the situation resolves itself within one activation interval.

Notice that a member does not receive this advisory if it is either inactive or about to deactivate.

## Diagnosis

This warning can indicate any of several situations:

| • | A network separates into two or more disconnected parts, and then reconnects.

Rendezvous fault tolerance software arranges for the correct number of active members on each disconnected part of the network. When the parts reconnect, the active members with the lowest rank become extraneous, and quickly deactivate. This warning indicates that a network problem occurred.

| • | Members have different active goal parameters.

If member A has an active goal of one member, and B has an active goal of two members, then A and B will both become active, and A receives this complaint that too many members are active. (Both A and B also receive the `PARAM_MISMATCH` error advisory, with `Active goal differs` in the `RVADV_DESC` field.)

| • | Interval parameters to Rendezvous fault tolerance software are too short compared to the speed of the hardware clock and operating system services.

See Step 4: Choose the Intervals.

| • | The active member did not send timely heartbeat messages. For example, a callback function blocked, or did not return promptly, delaying the heartbeat messages.

See Ensure Timely Event Processing.

## Message Fields

Field Name | Description
`RVADV_DESC` | A string describing the specific situation of this advisory. This field has datatype `TIBRVMSG_STRING.`

## See Also

Fault Tolerance Concepts.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2023. Cloud Software Group, Inc. All Rights Reserved.