From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: [hail patch 5/7] Drop a per-key message
Date: Thu, 29 Jul 2010 20:50:18 -0600 [thread overview]
Message-ID: <20100729205018.78e0e518@lembas.zaitcev.lan> (raw)
Not a good idea on a working server with thousands of keys.
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
---
server/replica.c | 7 -------
1 file changed, 7 deletions(-)
commit cc860ab6272571320f6be4651107da90141dcfb8
Author: Pete Zaitcev <zaitcev@yahoo.com>
Date: Thu Jul 29 19:38:38 2010 -0600
Drop a per-key printout.
diff --git a/server/replica.c b/server/replica.c
index e774824..ac14cb2 100644
--- a/server/replica.c
+++ b/server/replica.c
@@ -601,13 +601,6 @@ static void rep_scan_verify(struct rep_arg *arg,
oid = GUINT64_FROM_LE(obj->d.a.oid);
- applog(LOG_INFO, "bucket %s key %s oid %llX n(%u,%u,%u): all %d ok %d",
- bucket_name, object_name, (long long) oid,
- GUINT32_FROM_LE(obj->d.a.nidv[0]),
- GUINT32_FROM_LE(obj->d.a.nidv[1]),
- GUINT32_FROM_LE(obj->d.a.nidv[2]),
- allcnt, redcnt);
-
if (redcnt < MAXWAY) { /* maybe have MINWAY too? */
rep_job_start(arg, cp->klen, cp->key, oid,
GUINT64_FROM_LE(obj->size), redcnt, redvec);
reply other threads:[~2010-07-30 2:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100729205018.78e0e518@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).