If only one node is out of sync, how far out of sync is it?
What patch level are you on (sql edition, patch and cu please)?
Is it a readable secondary?
Is your log file growing on the primary?
Before taking action, these are important questions to answer. If the log file is growing for instance you may need to go down the path that Perry has suggested. If not, this may be related to a CU that was recently released.
It could also be a stuck thread that gets released and allows the secondary to immediately resync just by bouncing the SQL Service on that instance.
Also, it does happen every once in a while that you just need to right click the database on the secondary and select the option to start sync'ing. Applying windows patches will occasionally pause the sync.
I have given a name to my pain...MCM SQL Server, MVP
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events