| Issue 2943: | Strange replication message in gerrit log after upgrade to 2.9.1 | |
| 1 person starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: 2.9.1 What steps will reproduce the problem? 1. Push a new change from Gerrit to git 2. CHeck log file for replication 3. What is the expected output? What do you see instead? Please provide any additional information below. This morning I upgraded from Gerrit 2.8.5 to 2.9.1 We have one active Gerrit server and another server in a different location where Gerrit is installed but not running The replication is set up to replicate changes from the active server to the other machine We also sync the sql logs, so in case we have to we can deactivate the one server and switch over to the other server After the upgrade I pushed one change and then saw following in the error_log file on the Gerrit server: [2014-10-04 14:42:33,360] INFO com.googlesource.gerrit.plugins.replication.ReplicationQueue : Push to ssh://gerrit2@usbrgt01/gitstore/gerrit0/platform.git references: [RemoteRefUpdate[remoteName=refs/heads/develop, NOT_ATTEMPTED, (null)...4ff666ffab73c69546a1d4a847d6086835994671, srcRef=refs/heads/develop, message=null], RemoteRefUpdate[remoteName=refs/changes/25/11225/3, NOT_ATTEMPTED, (null)...4ff666ffab73c69546a1d4a847d6086835994671, srcRef=refs/changes/25/11225/3, message=null]] When I check on the other machine I see the acceptance of the public key for the gerrit userid and when cloning directly from the git repository on the other machine the changes are there The replication.config file contains: [remote "usbrgt01"] url = ssh://gerrit2@usbrgt01/gitstore/gerrit0/${name}.git mirror = true threads = 3 Why do I see this message in the Gerrit error log??
Oct 5, 2014
#1
Reinhard...@gmail.com
Oct 8, 2014
This message is an info message, replication plugin is more verbose in 2.9. In gerrit 2.10, it is even more verbose but all the replication logs are in a separate file so you will no longer see those in error log.
Status:
AwaitingInformation
Oct 8, 2014
(No comment was entered for this change.)
Status:
WontFix
Oct 9, 2014
I figured out that it is an info message only However it is misleading as it says something has not been done What does it mean exactly? Where is the documentation for the replication plugin that explains the verbosity and the meaning of the output?
Feb 19, 2015
Hi , Facing similar problem. can some one help me to understand the logs below... ============= [2015-02-20 08:15:22,826] [5337c2ec] Rescheduling replication to ssh://<remote_url> to avoid collision with an in-flight push. [2015-02-20 08:15:22,826] [5337c2ec] Rescheduling replication to ssh://<remote_url> to avoid collision with an in-flight push. [2015-02-20 08:15:22,826] [5337c2ec] Replication to ssh://<remote_url> started... [2015-02-20 08:15:27,194] [5337c2ec] Push to ssh://<remote_url> references: [RemoteRefUpdate[remoteName=refs/heads/release_merged, NOT_ATTEMPTED, (null)...c6924db06f7e5595900e625ec9b8897caf11eb00, srcRef=refs/heads/release_merged, forceUpdate, message=null], RemoteRefUpdate[remoteName=refs/heads/release, NOT_ATTEMPTED, (null)...ba94c82fe18222d5f0f8b07b020ddf0983be547d, srcRef=refs/heads/release, forceUpdate, message=null], RemoteRefUpdate[remoteName=refs/heads/release_delivered, NOT_ATTEMPTED, (null)...ba94c82fe18222d5f0f8b07b020ddf0983be547d, srcRef=refs/heads/release_delivered, forceUpdate, message=null]] [2015-02-20 08:16:22,959] [5337c2ec] Replication to ssh://<remote_url> completed in 60133 ms =========================== In particularly what does "NOT_ATTEMPTED, (null)" mean , and the last line "Replication --- completed" does not say what actually been replicated. |
|
| ► Sign in to add a comment |