I've has this message 4 times in the past month on a SQL2008 R2 server. No performance issues so it seems pretty harmless.