Tickets :: [#10026] Node and memcache

125	romulo (dot) pires123 (at) gmail (dot) com	Comment #4	Reply to this comment
Horde has no control over what data is cached to what node. If memcache nodes are inconsistent across a cluster, that is a PHP bug. Not is a bug, because for some reason the hord not update only the msg flags. I found a solution if the memcached config in horde not have one prefix, the horde put the server ip as one prefix!

153	romulo (dot) pires123 (at) gmail (dot) com	Comment #3	Reply to this comment
Horde has no control over what data is cached to what node. If memcache nodes are inconsistent across a cluster, that is a PHP bug. Not is a bug, because for some reason the hord not update only the msg flags.

254	Michael Slusarz	Comment #2 State ⇒ Not A Bug	Reply to this comment
Horde has no control over what data is cached to what node. If memcache nodes are inconsistent across a cluster, that is a PHP bug.

528	romulo (dot) pires123 (at) gmail (dot) com	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Base Due ⇒ 5/2/11 Summary ⇒ Node and memcache Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
I'm using memcached to cache messages. but in our structure we We use three nodes to maintain stability. I realized that for every node the horde is writing a cache of messages differently. That is a node I have two unread messages, but if I refresh the page I see that I have only one.