[ 
https://issues.apache.org/jira/browse/JCS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Smuts closed JCS-10.
--------------------------


> Remote Cache Events Are Lost Between Primary Failure and Failover Connection
> ----------------------------------------------------------------------------
>
>                 Key: JCS-10
>                 URL: https://issues.apache.org/jira/browse/JCS-10
>             Project: JCS
>          Issue Type: Improvement
>          Components: RMI Remote Cache
>    Affects Versions: jcs-1.2.7.8, jcs-1.2.7.9
>         Environment: All
>            Reporter: Aaron Smuts
>            Assignee: Aaron Smuts
>
> When the remote cache client encounters an error communicating with the 
> server it substitutes a balking facade (a zombie) for the service and then 
> initiates the failover / recovery process.  Events on the remote cache event 
> queue are sent to the zombie during the period between the failure and the 
> failover connection.  The Zombie simply balks.  Hence the events are lost.  
> In an environment with a failover--a hot standby--remote server, this is not 
> desireable.  It would be better if no events were lost to the Zombie.  
> The best solution is to make the Zombie a bounded queue.  Events that flood 
> into the Zombie should be put to the failover or the primary when the 
> connection is established.  The Zombie must be capable of limiting the size 
> of this queue.  When the remote cache restore process sets the remote server 
> handle on client, the client should check to see if if the current handle is 
> a zombie.  If the current server is a zombie, it should put into service the 
> good server and then walk the zombie queue.  
> Since failover switching is very quick, few items should be queued.  
> When handle error is called, the event should be passed to the zombie so it 
> is not lost.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jcs-dev-h...@jakarta.apache.org

Reply via email to