# Installing alongside Cassandra **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2011, 9:21pm UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619 "2011-10-17T21:21:46Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Anthony\_Ikeda](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@Anthony\_Ikeda](https://discuss.elastic.co/u/Anthony_Ikeda)\ **Post date:** [October 17, 2011, 9:21pm UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/1 "2011-10-17T21:21:46Z")
We are looking at using elastic search to index our data that we currently store to Cassandra. I was wondering if there are any concerns running elastic search on the same nodes that we use for Cassandra? Also which ports are required to be opened for proper communication from node to node and client to node? Anthony ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 17, 2011, 11:55pm UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/2 "2011-10-17T23:55:43Z")
On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \<[anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com) > wrote: > We are looking at using Elasticsearch to index our data that we > currently store to Cassandra. I was wondering if there are any > concerns running Elasticsearch on the same nodes that we use for > Cassandra? Running them on the same machine is possible, but, they will affect each other (IO, network, CPU). > Also which ports are required to be opened for proper communication > from node to node and client to node? By default, elasticsearch will use post 9300 for node to node and Java API communication, and port 9200 for HTTP endpoint. > Anthony ---
**Author:** ![Anthony\_Ikeda](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@Anthony\_Ikeda](https://discuss.elastic.co/u/Anthony_Ikeda)\ **Post date:** [October 18, 2011, 12:02am UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/3 "2011-10-18T00:02:05Z")
Thanks Shay. Also as for the ports, I set up a basic cluster in our dev environment, as far as I know there are no blocked ports, but trying to index any data leaves the Client hanging - no errors are reported thus the question about what ports need to be opened. Running locally works fine though. Anthony On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > We are looking at using Elasticsearch to index our data that we > > currently store to Cassandra. I was wondering if there are any > > concerns running Elasticsearch on the same nodes that we use for > > Cassandra? > > Running them on the same machine is possible, but, they will affect each > other (IO, network, CPU). > > > Also which ports are required to be opened for proper communication > > from node to node and client to node? > > By default, elasticsearch will use post 9300 for node to node and Java API > communication, and port 9200 for HTTP endpoint. > > > Anthony ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 18, 2011, 12:11am UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/4 "2011-10-18T00:11:57Z")
Which client are you using? Have the different nodes found each other and formed a cluster (you can see that in the logs, or the cluster state API)? One of the reasons why it might "hang" (not really hang, but wait for a timeout fo 1m) is if there aren't enough active shards for hte document to be indexed. This can happen, for example, if you have 1 node, and set number\_of\_replicas to 2 (3 copies), and then try and index a doc. By default, it expects a quorum of shards to be active. See write consistency in the index API docs: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)wrote: > Thanks Shay. Also as for the ports, I set up a basic cluster in our dev > environment, as far as I know there are no blocked ports, but trying to > index any data leaves the Client hanging - no errors are reported thus the > question about what ports need to be opened. > > Running locally works fine though. > > Anthony > > On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > We are looking at using Elasticsearch to index our data that we > > > currently store to Cassandra. I was wondering if there are any > > > concerns running Elasticsearch on the same nodes that we use for > > > Cassandra? > > > > Running them on the same machine is possible, but, they will affect each > > other (IO, network, CPU). > > > > > Also which ports are required to be opened for proper communication > > > from node to node and client to node? > > > > By default, elasticsearch will use post 9300 for node to node and Java API > > communication, and port 9200 for HTTP endpoint. > > > > > Anthony ---
**Author:** ![Anthony\_Ikeda](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@Anthony\_Ikeda](https://discuss.elastic.co/u/Anthony_Ikeda)\ **Post date:** [October 18, 2011, 12:39am UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/5 "2011-10-18T00:39:26Z")
I using the Java API. I seem to get these RemoteTransportExceptions: org.elasticsearch.transport.RemoteTransportException: [Georgianna Castleberry][inet[/10.130.202.34:9300]][indices/index/shard/index] Caused by: org.elasticsearch.action.UnavailableShardsException: [registry][4] [2] shardIt, [0] active : Timeout waiting for [1m], request: index... at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout( TransportShardReplicationOperationAction.java:455)195297 [main][au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer.testRegistryIndexer( TestRegistryIndexer.java:44)] DEBUG au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer - Indexed [REG:e3a05447-d481-406a-a135-627c21d0c903] at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( InternalClusterService.java:305) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) It just seems to sit there and every now and then it will proceed but hang again. Anthony On Mon, Oct 17, 2011 at 5:11 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Which client are you using? Have the different nodes found each other and > formed a cluster (you can see that in the logs, or the cluster state API)? > > One of the reasons why it might "hang" (not really hang, but wait for a > timeout fo 1m) is if there aren't enough active shards for hte document to > be indexed. This can happen, for example, if you have 1 node, and set > number\_of\_replicas to 2 (3 copies), and then try and index a doc. By > default, it expects a quorum of shards to be active. See write consistency > in the index API docs: > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). > > On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda \< > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > Thanks Shay. Also as for the ports, I set up a basic cluster in our dev > > environment, as far as I know there are no blocked ports, but trying to > > index any data leaves the Client hanging - no errors are reported thus the > > question about what ports need to be opened. > > > > Running locally works fine though. > > > > Anthony > > > > On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > > > We are looking at using Elasticsearch to index our data that we > > > > currently store to Cassandra. I was wondering if there are any > > > > concerns running Elasticsearch on the same nodes that we use for > > > > Cassandra? > > > > > > Running them on the same machine is possible, but, they will affect each > > > other (IO, network, CPU). > > > > > > > Also which ports are required to be opened for proper communication > > > > from node to node and client to node? > > > > > > By default, elasticsearch will use post 9300 for node to node and Java > > > API communication, and port 9200 for HTTP endpoint. > > > > > > > Anthony ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 18, 2011, 3:57am UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/6 "2011-10-18T03:57:35Z")
How do you construct the client? Are you sure its connected to the cluster? When you create the registry index, has it been properly allocated (check the cluster state or health API). On Tue, Oct 18, 2011 at 2:39 AM, Anthony Ikeda [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)wrote: > I using the Java API. > > I seem to get these RemoteTransportExceptions: > > org.elasticsearch.transport.RemoteTransportException: [Georgianna > Castleberry][inet[/10.130.202.34:9300]][indices/index/shard/index] > > Caused by: org.elasticsearch.action.UnavailableShardsException: > [registry][4] [2] shardIt, [0] active : Timeout waiting for [1m], request: > index... > > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout( > TransportShardReplicationOperationAction.java:455)195297 > [main][au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer.testRegistryIndexer( > TestRegistryIndexer.java:44)] DEBUG > au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer - > Indexed [REG:e3a05447-d481-406a-a135-627c21d0c903] > > at > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( > InternalClusterService.java:305) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > ThreadPoolExecutor.java:886) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:908) > > at java.lang.Thread.run(Thread.java:662) > > It just seems to sit there and every now and then it will proceed but hang > again. > > Anthony > > On Mon, Oct 17, 2011 at 5:11 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Which client are you using? Have the different nodes found each other and > > formed a cluster (you can see that in the logs, or the cluster state API)? > > > > One of the reasons why it might "hang" (not really hang, but wait for a > > timeout fo 1m) is if there aren't enough active shards for hte document to > > be indexed. This can happen, for example, if you have 1 node, and set > > number\_of\_replicas to 2 (3 copies), and then try and index a doc. By > > default, it expects a quorum of shards to be active. See write consistency > > in the index API docs: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). > > > > On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda \< > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > Thanks Shay. Also as for the ports, I set up a basic cluster in our dev > > > environment, as far as I know there are no blocked ports, but trying to > > > index any data leaves the Client hanging - no errors are reported thus the > > > question about what ports need to be opened. > > > > > > Running locally works fine though. > > > > > > Anthony > > > > > > On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > > > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > > > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > > > > > We are looking at using Elasticsearch to index our data that we > > > > > currently store to Cassandra. I was wondering if there are any > > > > > concerns running Elasticsearch on the same nodes that we use for > > > > > Cassandra? > > > > > > > > Running them on the same machine is possible, but, they will affect each > > > > other (IO, network, CPU). > > > > > > > > > Also which ports are required to be opened for proper communication > > > > > from node to node and client to node? > > > > > > > > By default, elasticsearch will use post 9300 for node to node and Java > > > > API communication, and port 9200 for HTTP endpoint. > > > > > > > > > Anthony ---
**Author:** ![Anthony\_Ikeda](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@Anthony\_Ikeda](https://discuss.elastic.co/u/Anthony_Ikeda)\ **Post date:** [October 18, 2011, 9:20pm UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/7 "2011-10-18T21:20:34Z")
At the moment I have a Member variable of Client with a getClient private method: public class ElasticRegistryIndexer implements RegistryIndexer { ``` private Logger mLog = Logger.getLogger(getClass()); private Client mClient; private Client getClient() { if (mClient == null) { Properties settingsMap = new Properties(); settingsMap.put("cluster.name", "registry_foundation"); settingsMap.put("client.transport.sniff", "true"); Settings settings = ``` ImmutableSettings.settingsBuilder().put(settingsMap).build(); ``` mClient = new TransportClient(settings); ((TransportClient)mClient).addTransportAddress(newInetSocketTransportAddress( ``` "10.130.202.34", 9300)); ``` ((TransportClient)mClient).addTransportAddress(newInetSocketTransportAddress( ``` "10.130.202.35", 9300)); // ((TransportClient)mClient).addTransportAddress(new InetSocketTransportAddress("192.168.202.235", 9300)); ``` ClusterHealthRequest healthRequest = newClusterHealthRequest(); ClusterHealthResponse response = mClient.admin().cluster().health(healthRequest).actionGet(); for (ClusterIndexHealth health :response) { mLog.debug(health.getIndex()); } } return mClient; } ``` I haven't ben able to find any suitable docs on how to manage the client properly as yet. Anthony On Mon, Oct 17, 2011 at 8:57 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > How do you construct the client? Are you sure its connected to the cluster? > When you create the registry index, has it been properly allocated (check > the cluster state or health API). > > On Tue, Oct 18, 2011 at 2:39 AM, Anthony Ikeda \< > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > I using the Java API. > > > > I seem to get these RemoteTransportExceptions: > > > > org.elasticsearch.transport.RemoteTransportException: [Georgianna > > Castleberry][inet[/10.130.202.34:9300]][indices/index/shard/index] > > > > Caused by: org.elasticsearch.action.UnavailableShardsException: > > [registry][4] [2] shardIt, [0] active : Timeout waiting for [1m], request: > > index... > > > > at > > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout( > > TransportShardReplicationOperationAction.java:455)195297 > > [main][au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer.testRegistryIndexer( > > TestRegistryIndexer.java:44)] DEBUG > > au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer - > > Indexed [REG:e3a05447-d481-406a-a135-627c21d0c903] > > > > at > > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( > > InternalClusterService.java:305) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > > ThreadPoolExecutor.java:886) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > ThreadPoolExecutor.java:908) > > > > at java.lang.Thread.run(Thread.java:662) > > > > It just seems to sit there and every now and then it will proceed but hang > > again. > > > > Anthony > > > > On Mon, Oct 17, 2011 at 5:11 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > Which client are you using? Have the different nodes found each other and > > > formed a cluster (you can see that in the logs, or the cluster state API)? > > > > > > One of the reasons why it might "hang" (not really hang, but wait for a > > > timeout fo 1m) is if there aren't enough active shards for hte document to > > > be indexed. This can happen, for example, if you have 1 node, and set > > > number\_of\_replicas to 2 (3 copies), and then try and index a doc. By > > > default, it expects a quorum of shards to be active. See write consistency > > > in the index API docs: > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). > > > > > > On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda \< > > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > > > Thanks Shay. Also as for the ports, I set up a basic cluster in our dev > > > > environment, as far as I know there are no blocked ports, but trying to > > > > index any data leaves the Client hanging - no errors are reported thus the > > > > question about what ports need to be opened. > > > > > > > > Running locally works fine though. > > > > > > > > Anthony > > > > > > > > On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > > > > > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > > > > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > > > > > > > We are looking at using Elasticsearch to index our data that we > > > > > > currently store to Cassandra. I was wondering if there are any > > > > > > concerns running Elasticsearch on the same nodes that we use for > > > > > > Cassandra? > > > > > > > > > > Running them on the same machine is possible, but, they will affect > > > > > each other (IO, network, CPU). > > > > > > > > > > > Also which ports are required to be opened for proper communication > > > > > > from node to node and client to node? > > > > > > > > > > By default, elasticsearch will use post 9300 for node to node and Java > > > > > API communication, and port 9200 for HTTP endpoint. > > > > > > > > > > > Anthony ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 18, 2011, 9:32pm UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/8 "2011-10-18T21:32:06Z")
ok, so you use the transport client (thats what I wanted to know, if its the transport client or hte node client). The way you construct it looks good. When you create the registry index, how many shards and how many replicas do you have? How many nodes to you have in your cluster? On Tue, Oct 18, 2011 at 2:39 AM, Anthony Ikeda [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)wrote: > I using the Java API. > > I seem to get these RemoteTransportExceptions: > > org.elasticsearch.transport.RemoteTransportException: [Georgianna > Castleberry][inet[/10.130.202.34:9300]][indices/index/shard/index] > > Caused by: org.elasticsearch.action.UnavailableShardsException: > [registry][4] [2] shardIt, [0] active : Timeout waiting for [1m], request: > index... > > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout( > TransportShardReplicationOperationAction.java:455)195297 > [main][au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer.testRegistryIndexer( > TestRegistryIndexer.java:44)] DEBUG > au.com.ikeda.testing.ground.foundation.service.TestRegistryIndexer - > Indexed [REG:e3a05447-d481-406a-a135-627c21d0c903] > > at > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run( > InternalClusterService.java:305) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > ThreadPoolExecutor.java:886) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:908) > > at java.lang.Thread.run(Thread.java:662) > > It just seems to sit there and every now and then it will proceed but hang > again. > > Anthony > > On Mon, Oct 17, 2011 at 5:11 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Which client are you using? Have the different nodes found each other and > > formed a cluster (you can see that in the logs, or the cluster state API)? > > > > One of the reasons why it might "hang" (not really hang, but wait for a > > timeout fo 1m) is if there aren't enough active shards for hte document to > > be indexed. This can happen, for example, if you have 1 node, and set > > number\_of\_replicas to 2 (3 copies), and then try and index a doc. By > > default, it expects a quorum of shards to be active. See write consistency > > in the index API docs: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_.html). > > > > On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda \< > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > Thanks Shay. Also as for the ports, I set up a basic cluster in our dev > > > environment, as far as I know there are no blocked ports, but trying to > > > index any data leaves the Client hanging - no errors are reported thus the > > > question about what ports need to be opened. > > > > > > Running locally works fine though. > > > > > > Anthony > > > > > > On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > > > On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda \< > > > > [anthony.ikeda.dev@gmail.com](mailto:anthony.ikeda.dev@gmail.com)\> wrote: > > > > > > > > > We are looking at using Elasticsearch to index our data that we > > > > > currently store to Cassandra. I was wondering if there are any > > > > > concerns running Elasticsearch on the same nodes that we use for > > > > > Cassandra? > > > > > > > > Running them on the same machine is possible, but, they will affect each > > > > other (IO, network, CPU). > > > > > > > > > Also which ports are required to be opened for proper communication > > > > > from node to node and client to node? > > > > > > > > By default, elasticsearch will use post 9300 for node to node and Java > > > > API communication, and port 9200 for HTTP endpoint. > > > > > > > > > Anthony ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:51am UTC](https://discuss.elastic.co/t/installing-alongside-cassandra/5619/9 "2017-07-06T03:51:27Z")