From e5f0f8122fa9c2e0ff115f96518f021b19299d05 Mon Sep 17 00:00:00 2001
From: Spencer Krum <nibz@spencerkrum.com>
Date: Wed, 6 Jan 2016 11:49:34 -0800
Subject: [PATCH] Hound Maintenance

Change-Id: Ice50b20a0418a21b5e778c2433132a627ac73146
---
 doc/source/codesearch.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/source/codesearch.rst b/doc/source/codesearch.rst
index 346d572148..a50a0bc3bb 100644
--- a/doc/source/codesearch.rst
+++ b/doc/source/codesearch.rst
@@ -30,3 +30,15 @@ Overview
 Hound is configured to read projects from a config.json file that is
 automatically generated from the Gerrit projects.yaml, defined in the
 $::project_config::jeepyb_project_file variable in Puppet.
+
+
+Maintenance
+===========
+
+Hound uses 'git pull' to keep repos in sync. If a force push is ever used to
+correct an issue in a repo, then hound will not be able to pull or index those
+changes. The only way to detect this is to look in /var/log/hound.log. The
+error message looks like hound attempting to update the repo and getting a
+'remote host hung up' message. The issue can be corrected by an infra-root
+removing the relevant hound data directory. Hound will re-clone with the new
+history.