Hi Bakary,
The timeout you are seeing is probably due to the JDBC driver of your
database that uses a TCP connection and waits for the TCP timeout to
expire. For more reactivity you can either tune the TCP timeouts of your
operating system or use a WaitForCompletion policy set to 'first' (check
your sequoia.dtd for details).
The recovery procedure for a crashed backend is detailed at
http://sequoia.continuent.org/doc/infocenter/topic/org.continuent.sequoia.doc/html/Recover_from_a_database_server_node_failure.html
Hope this helps,
Emmanuel
I am testing the transparency failover.
I shutdow host without disableling his corresponding backend and send
requests to controller.
First I have connection time out. seconde the controller execute
request on the others nodes.
I restart host again but the controller do nothing on this. Is the
thinks (config) to do before to restore the state.
What is the best config for this, please?
Here is my config:
<RequestManager>
<RequestScheduler>
<RAIDb-1Scheduler level="passThrough"/> instead of
optimisticTransaction
</RequestScheduler>
<RequestCache>
<MetadataCache/>
<ParsingCache/>
<ResultCache granularity="table" />
</RequestCache>
<LoadBalancer>
<RAIDb-1>
<RAIDb-1-RoundRobin/>
</RAIDb-1>
</LoadBalancer>
...
</RequestManagerW>
--
Bakary,
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [email protected]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
