There's no internal process that generates PUT's. The replicator (which is just another external client) will make checkpoints, but those are of the form /dbname/_local/<md5>, which doesn't match what you're seeing. I suggest a packet sniffer to trace the source of these PUT requests, probably some test script, etc. The contents of '/my_db/abb7d77bcaf04e25eb84b6f93f6e535b' might be a strong clue too.
B. On 21 March 2012 02:37, Michael Parker <[email protected]> wrote: > I recently set up Monit with the CouchDB plugin, and was surprised to > find that we had a steady stream of PUT requests to our server. Our > stack is Apache -> Django+CouchDBKit -> CouchDB, and our Apache and > Django logs don't see any external PUT requests (which is expected > because we haven't launched yet). Pulling up Futon at /_util/ I can > see that the number of documents in our database is remaining > constant, but the size and update sequence is steadily increasing, > which is consistent with receiving many PUTs. Redacting the database > and view names (sorry), the couch.log file looks like: > > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.135.0>] checkpointing view > update at seq 4236365 for my_db _design/api > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'GET' /my_db/_design/api/_view/my_view?key=%2214156997551%22&include_docs=true > 200 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'PUT' /my_db/f5aa0fa8efef548afd1ec7bcab5a5b99 201 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.135.0>] checkpointing view > update at seq 4236366 for my_db _design/api > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'GET' /my_db/_design/api/_view/my_view?key=%2213234222771%22&include_docs=true > 200 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'PUT' /my_db/1b0dc0469699f9540e19d7b6f321276a 201 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.135.0>] checkpointing view > update at seq 4236367 for my_db _design/api > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'GET' /my_db/_design/api/_view/my_view?key=%2213233870234%22&include_docs=true > 200 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'PUT' /my_db/0b58ce973d617c706b0d5efaf23644e8 201 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.135.0>] checkpointing view > update at seq 4236368 for my_db _design/api > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'GET' /my_db/_design/api/_view/my_view?key=%2216504650525%22&include_docs=true > 200 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.29622.12>] 127.0.0.1 - - > 'PUT' /my_db/abb7d77bcaf04e25eb84b6f93f6e535b 201 > [Wed, 21 Mar 2012 02:29:07 GMT] [info] [<0.135.0>] checkpointing view > update at seq 4236369 for my_db _design/api > > And so forth. What internally could be generating these PUTs? We are > not replicating the database, at least to the best of my knowledge. > > Thanks, > Mike
