Bug 810302 - have agent config setting to test or not to test failover list on startup
Summary: have agent config setting to test or not to test failover list on startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ---
: RHQ 4.4.0
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-05 14:59 UTC by John Mazzitelli
Modified: 2013-09-01 10:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 10:18:44 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 810124 0 high CLOSED Agent registration taking more than a minute makes plugins update at startup fail 2021-02-22 00:41:40 UTC

Internal Links: 810124

Description John Mazzitelli 2012-04-05 14:59:25 UTC
We need to add a new agent configuration property:

rhq.agent.test-failover-list-at-startup

by default it is true (since that is what we do today).

This will skip the call to AgentMan.testFailoverList if its false.

This could help speed up agent startup.

Comment 1 John Mazzitelli 2012-04-05 15:15:04 UTC
we need to also add some debug log messages to the testFailoverList in case that is slowing things down, we'll at least see the connection attempts causing problems

Comment 2 John Mazzitelli 2012-04-05 18:33:00 UTC
if the new setting is set to true (which is the default) the agent log will now show one log message per failover list entry that looks like this:

2012-04-05 14:27:37,624 DEBUG [RHQ Agent Registration Thread] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.test-failover-list-entry}Testing failover connectivity to server [myserver:7080]

If the connectivity test fails, you will see a error messages (this has always been the case, I just added the debug message that I document above).

If the new setting it set to false, the testing of failover entries is skipped and you will instead see this message in the log file:

   "Testing connectivity to servers found in the failover list has been DISABLED and will be skipped."

NOTE: if all servers in the failover list fail the connectivity check, you will see this error message dumped on the agent console window (this has always been the case, I'm just documenting it here):

"!!! There are [{0}] servers that are potentially unreachable by this agent.
Please double check all public endpoints of your servers and ensure
they are all reachable by this agent. The failed server endpoints are:
{the failover list is shown here}
See the Administration (Topology) > Servers in the server GUI
to change the public endpoint of a server.
THIS AGENT WILL WAIT UNTIL ONE OF ITS SERVERS BECOMES REACHABLE!"

Comment 3 John Mazzitelli 2012-04-05 18:48:50 UTC
git commit to master a8f774500b02d7adbf59a0ed4995d8cdd8a4b9c6

Comment 4 John Mazzitelli 2012-05-03 14:26:05 UTC
will make the default "false" to avoid any potential problems. leaving it open for the user to flip this to true so they can do some debugging if need be

Comment 5 John Mazzitelli 2012-05-03 16:20:16 UTC
(In reply to comment #4)
> will make the default "false" to avoid any potential problems. leaving it open
> for the user to flip this to true so they can do some debugging if need be

git commit master : 3c3b4e0

to test this feature, you now have to set to "true" the config preference - "rhq.agent.test-failover-list-at-startup"

Comment 6 John Mazzitelli 2012-08-03 14:29:49 UTC
fyi: a8f774500b02d7adbf59a0ed4995d8cdd8a4b9c6 and 3c3b4e0 where cherry picked already to release/jon3.1.0 branch

Comment 7 Heiko W. Rupp 2013-09-01 10:18:44 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


Note You need to log in before you can comment on or make changes to this bug.