Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have a stacked, three node cluster running 8.3.11 with a stand-alone proxy server. I use protocol C on the lower level and A on the stacked. For several weeks I ran the proxy with compression disabled with no problems. When I enabled compression on the proxy I also had to enable ahead / behind mode for the stacked resources so my primary node doesn't block with the proxy falls behind. This of course means that I see regular resyncs during activity spikes. I've only been running this way for a few days now but twice when I've checked on things in the morning I will find my primary resource showing SyncSource 100% UpToDate/Inconsistent on the primary node but everything looking normal on the secondary node. I resolve the issue by disconnecting / reconnecting that resource from the secondary node. Any ideas why it would get stuck at 100% on a resync from time to time? -- J.R. Lillard System / Network Admin Web Programmer Golden Heritage Foods 120 Santa Fe St. Hillsboro, KS 67063 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120917/de3cd676/attachment.htm>