Couchbase affected by the lead second bug? / Memcached process CPU pegged 100% of CPUs

Reproduced in the hope it can help figure out the problem to anyone else.

My community couchbase installation on AWS EC2 Ubuntu linux starting using CPU like crazy the night of the 1st of July. Checking the log files there was nothing strange going on there. Process "memcached" changed from being idle to CPU pegged on all the machine CPUs.

Restarting the amazon EC2 instances solved the problem, however, the description of the problem and the time it occurred is consistent with the leap second bug with affects MySql and firefox on linux among others. If so, it might be possible to fix it without restarting following the instructions reproduced bellow. As I said, this is untested as I rebooted my instances:

(UNTESTED, you will need to stop the NTPD daemon first)

date -s "`date`"

More info about the leap second bug:

http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu...
http://blog.wpkg.org/2012/07/01/java-leap-second-bug-30-june-1-july-2012...