Hi Bulut,
I don't see anything obviously wrong with your cluster configuration. I used the same example cluster configuration file and started two nodes. Since I didn't have a "log4j.properties" when I started the nodes, all of the logging went to stdout but in this logging I can see it took awhile (almost 2 minutes) for the nodes to discover each other:
Sep 26 2014 07:24:02.253 INFO hz._hzInstance_1_esp_multi.cached.thread-5 com.sybase.esp.cluster.impl.CacheService - CODE_700102 | Membership listener...memberRemoved Member [127.0.0.1]:19001
Sep 26 2014 07:24:02.254 INFO hz._hzInstance_1_esp_multi.cached.thread-5 com.sybase.esp.cluster.impl.CacheService - CODE_700103 | Membership listener cleaning up member Member [127.0.0.1]:19001
Sep 26 2014 07:25:56.546 INFO hz._hzInstance_1_esp_multi.cached.thread-3 com.sybase.esp.cluster.impl.CacheService - CODE_700101 | Membership listener...memberAdded Member [10.7.119.177]:19003 this
Sep 26 2014 07:26:02.557 INFO hz._hzInstance_1_esp_multi.cached.thread-3 com.sybase.esp.cluster.impl.CacheService - CODE_700101 | Membership listener...memberAdded Member [127.0.0.1]:19001
It may have taken two minutes because I am working remotely on a VPN today I'm not sure. I'll be traveling for the next week so I won't be able to investigate further.
If you don't see anything obvious in each node's stdout logging, you may need to modify your start_node.sh/start_node.bat to be more like the one in $ESP_HOME/cluster/config/esp1 where it uses a "log4j.properties" type file and change all of the "info" references to "debug":
% grep LOG start_node.sh
ESP_CLUSTER_LOG_PROPERTIES=cluster.log.properties
ESP_CLUSTER_NODE_LOG_FILE=$ESP_CLUSTER_NODE_NAME.log
"$ESP_HOME/bin/esp_cluster_node" -p$ESP_CLUSTER_LOG_PROPERTIES -f$ESP_CLUSTER_NODE_LOG_FILE --config $ESP_CLUSTER_CONFIG --node-name $ESP_CLUSTER_NODE_NAME
Only a wild guess, you might check your two Linux boxes to see if they have a proxy between them that would prevent easy from communicating:
% env | grep proxy
http_proxy=http://proxy.acme.com:8080
https_proxy=http://proxy.acme.com:8080
ftp_proxy=http://proxy.acme.com:8080
no_proxy=archer.acme.com,localhost,127.0.0.1,archer2.acme.com,archer,10.7.119.177
As for when to use active-active? Maybe you have a project that performs some complex calculations and stores the results in a WINDOW. This project does not write the data anywhere but there are clients that subscribe to the WINDOW. You want the clients to always be able to subscribe to this window. One project goes down, the other is still running with an exact copy of the data.
Thanks,
Neal