Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Neha Dave]

Try
>cqlsh 

regards
Neha

On Mon, Sep 14, 2015 at 3:53 PM, Ajay Garg  wrote:

> Hi All.
>
> We have setup a Ubuntu-14.04 server, and followed the steps exactly as
> per http://wiki.apache.org/cassandra/DebianPackaging
>
> Installation completes fine, Cassandra starts fine, however cqlsh does not
> work.
> We get the error ::
>
>
> ###
> ajay@comp:~$ cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
> None")})
>
> ###
>
>
>
> Version-Info ::
>
>
> ###
> ajay@comp:~$ dpkg -l | grep cassandra
> ii  cassandra   2.1.9
>  all  distributed storage system for structured data
>
> ###
>
>
>
> The port "seems" to be opened fine.
>
>
> ###
> ajay@comp:~$ netstat -an | grep 9042
> tcp6   0  0 127.0.0.1:9042  :::*LISTEN
>
> ###
>
>
>
> Firewall-filters ::
>
>
> ###
> ajay@comp:~$ sudo iptables -L
> [sudo] password for ajay:
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
> DROP   all  --  anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
>
> ###
>
>
>
> Even telnet fails :(
>
>
> ###
> ajay@comp:~$ telnet localhost 9042
> Trying 127.0.0.1...
>
> ###
>
>
>
> Any ideas please?? We have been stuck on this for a good 3 hours now :(
>
>
>
> Thanks and Regards,
> Ajay
>

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ahmed Eljami]

Hi,

Can you pass the parametrs listen_adress, rpc_adress and brodcast_rpc_adress
from cassandra.yaml.

2015-09-14 11:23 GMT+01:00 Ajay Garg :

> Hi All.
>
> We have setup a Ubuntu-14.04 server, and followed the steps exactly as
> per http://wiki.apache.org/cassandra/DebianPackaging
>
> Installation completes fine, Cassandra starts fine, however cqlsh does not
> work.
> We get the error ::
>
>
> ###
> ajay@comp:~$ cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
> None")})
>
> ###
>
>
>
> Version-Info ::
>
>
> ###
> ajay@comp:~$ dpkg -l | grep cassandra
> ii  cassandra   2.1.9
>  all  distributed storage system for structured data
>
> ###
>
>
>
> The port "seems" to be opened fine.
>
>
> ###
> ajay@comp:~$ netstat -an | grep 9042
> tcp6   0  0 127.0.0.1:9042  :::*LISTEN
>
> ###
>
>
>
> Firewall-filters ::
>
>
> ###
> ajay@comp:~$ sudo iptables -L
> [sudo] password for ajay:
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
> DROP   all  --  anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
>
> ###
>
>
>
> Even telnet fails :(
>
>
> ###
> ajay@comp:~$ telnet localhost 9042
> Trying 127.0.0.1...
>
> ###
>
>
>
> Any ideas please?? We have been stuck on this for a good 3 hours now :(
>
>
>
> Thanks and Regards,
> Ajay
>



-- 
Cordialement;

Ahmed ELJAMI

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ahmed Eljami]

 In cassanrda.yaml:
listen_address:@ Of node
rpc_address:0.0.0.0

brodcast_rpc_address:@ Of node

2015-09-14 11:31 GMT+01:00 Neha Dave :

> Try
> >cqlsh 
>
> regards
> Neha
>
> On Mon, Sep 14, 2015 at 3:53 PM, Ajay Garg  wrote:
>
>> Hi All.
>>
>> We have setup a Ubuntu-14.04 server, and followed the steps exactly as
>> per http://wiki.apache.org/cassandra/DebianPackaging
>>
>> Installation completes fine, Cassandra starts fine, however cqlsh does
>> not work.
>> We get the error ::
>>
>>
>> ###
>> ajay@comp:~$ cqlsh
>> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
>> error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
>> None")})
>>
>> ###
>>
>>
>>
>> Version-Info ::
>>
>>
>> ###
>> ajay@comp:~$ dpkg -l | grep cassandra
>> ii  cassandra   2.1.9
>>  all  distributed storage system for structured data
>>
>> ###
>>
>>
>>
>> The port "seems" to be opened fine.
>>
>>
>> ###
>> ajay@comp:~$ netstat -an | grep 9042
>> tcp6   0  0 127.0.0.1:9042  :::*
>> LISTEN
>>
>> ###
>>
>>
>>
>> Firewall-filters ::
>>
>>
>> ###
>> ajay@comp:~$ sudo iptables -L
>> [sudo] password for ajay:
>> Chain INPUT (policy ACCEPT)
>> target prot opt source   destination
>> ACCEPT all  --  anywhere anywhere state
>> RELATED,ESTABLISHED
>> ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
>> DROP   all  --  anywhere anywhere
>>
>> Chain FORWARD (policy ACCEPT)
>> target prot opt source   destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target prot opt source   destination
>>
>> ###
>>
>>
>>
>> Even telnet fails :(
>>
>>
>> ###
>> ajay@comp:~$ telnet localhost 9042
>> Trying 127.0.0.1...
>>
>> ###
>>
>>
>>
>> Any ideas please?? We have been stuck on this for a good 3 hours now :(
>>
>>
>>
>> Thanks and Regards,
>> Ajay
>>
>
>


-- 
Cordialement;

Ahmed ELJAMI

cassandra-stress where query with greater than operator

[folex]

Hi All.

I'm trying to set up cassandra load testing and came up with the next YAML
config (https://gist.github.com/folex/d297cc8208a2e54a36d7) :

keyspace: stress

keyspace_definition: |
  CREATE KEYSPACE stress WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 3};

table: messages

table_definition: |
  CREATE TABLE stress.messages (
chat_id bigint,
uid_to bigint,
message_id bigint,
text blob,
uid blob,
PRIMARY KEY ((chat_id, uid_to), message_id)
  ) WITH CLUSTERING ORDER BY (message_id ASC)

columnspec:

  - name: text
size: gaussian(0..44)

  - name: uid
size: gaussian(0..32)

  - name: chat_id
size: uniform(0..64)
population: uniform(500..2K)

  - name: uid_to
size: uniform(0..64)
population: uniform(500..2K)

  - name: message_id
size: uniform(0..64)

insert:
  partitions: fixed(1)
  batchtype:  UNLOGGED
  select: fixed(1)/1

queries:
  scan:
cql: select * from stress.messages where chat_id = ? and uid_to = ? and
message_id > ? limit 50;
fields: samerow


Now, insert works as expectet, but "scan" just hangs up after printing out
stat headers.
Also I found that if I remove "and message_id > ?" part, scan start working.

Is that a known problem? How do I workaround that?

Thanks in advance.

- folex

Question: Gossip Protocol

[Thouraya TH]

Hi all,

Please, the gossip procotol in cassandra is running every ... seconds ?


Thank you so much for answers.
Best Regards.

Re: Question: Gossip Protocol

[Thouraya TH]

 I find this information :

The gossip process runs every second and exchanges state messages with up
to three other nodes in the cluster.

here
http://docs.datastax.com/en/cassandra/2.0/cassandra/architecture/architectureGossipAbout_c.html


Please, i ask if it is possible to change this periode, to three seconds ?

Kind regards.




2015-09-14 14:15 GMT+01:00 Thouraya TH :

> Hi all,
>
> Please, the gossip procotol in cassandra is running every ... seconds ?
>
>
> Thank you so much for answers.
> Best Regards.
>

Re: Importing data from SQL Server

[Raluca Marcu]

Kevin Burton  charter.net> writes:

> 
> I have seen numerous posts on transferring data from MySql to Cassandra 
but have yet to find a good way to
> transfer directly from a Microsoft SQL Server table to a Cassandra CF. 
Even better would be a method to take
> as input the output of an arbitrary SQL query. Ideas?
> 


Hello,

I realize this post is pretty old, but I was wondering if you found an 
answer to this question and if you've used it.
I have to load data from SQL Server into Cassandra and I am completely new 
to Cassandra and all of the posts I seem to be able to find are demos 
about loading from MySQL into Cassandra.
Any, any help would be extremely appreciated!
Thank you very much!
Raluca

Re: Importing data from SQL Server

[Jason Kushmaul]

I had to write my own, but not due to lack of support.  I found I needed to
preprocess the data before I put it into cassandra, you might find that
beneficial. I only had 3 massive tables to worry about so it wasn't that
much extra work to code it out - your case might be different if you have
50 tables, or if this needs to recur.

 If you don't need to preprocess the data, what you could probably do is
export your data from MSSQL to CSV (built into sql mgmt studio)
 and use CQL to import the CSV -
http://www.datastax.com/dev/blog/simple-data-importing-and-exporting-with-cassandra


On Mon, Sep 14, 2015 at 11:37 AM, Raluca Marcu  wrote:

>
> Kevin Burton  charter.net> writes:
>
> >
> > I have seen numerous posts on transferring data from MySql to Cassandra
> but have yet to find a good way to
> > transfer directly from a Microsoft SQL Server table to a Cassandra CF.
> Even better would be a method to take
> > as input the output of an arbitrary SQL query. Ideas?
> >
>
>
> Hello,
>
> I realize this post is pretty old, but I was wondering if you found an
> answer to this question and if you've used it.
> I have to load data from SQL Server into Cassandra and I am completely new
> to Cassandra and all of the posts I seem to be able to find are demos
> about loading from MySQL into Cassandra.
> Any, any help would be extremely appreciated!
> Thank you very much!
> Raluca
>
>
>
>
>
>


-- 
Jason Kushmaul | 517.899.7852
Engineering Manager

Re: Importing data from SQL Server

[Sebastian Estevez]

If you have a csv, try Brian's cassandra-loader. It is a full featured c*
java import program built with all the best practices for data loading and
writes.

https://github.com/brianmhess/cassandra-loader

All the best,


[image: datastax_logo.png] 

Sebastián Estévez

Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com

[image: linkedin.png]  [image:
facebook.png]  [image: twitter.png]
 [image: g+.png]





DataStax is the fastest, most scalable distributed database technology,
delivering Apache Cassandra to the world’s most innovative enterprises.
Datastax is built to be agile, always-on, and predictably scalable to any
size. With more than 500 customers in 45 countries, DataStax is the
database technology and transactional backbone of choice for the worlds
most innovative companies such as Netflix, Adobe, Intuit, and eBay.

On Mon, Sep 14, 2015 at 11:55 AM, Jason Kushmaul <
jkushm...@rocketfuelinc.com> wrote:

> I had to write my own, but not due to lack of support.  I found I needed
> to preprocess the data before I put it into cassandra, you might find that
> beneficial. I only had 3 massive tables to worry about so it wasn't that
> much extra work to code it out - your case might be different if you have
> 50 tables, or if this needs to recur.
>
>  If you don't need to preprocess the data, what you could probably do is
> export your data from MSSQL to CSV (built into sql mgmt studio)
>  and use CQL to import the CSV -
> http://www.datastax.com/dev/blog/simple-data-importing-and-exporting-with-cassandra
>
>
> On Mon, Sep 14, 2015 at 11:37 AM, Raluca Marcu 
> wrote:
>
>>
>> Kevin Burton  charter.net> writes:
>>
>> >
>> > I have seen numerous posts on transferring data from MySql to Cassandra
>> but have yet to find a good way to
>> > transfer directly from a Microsoft SQL Server table to a Cassandra CF.
>> Even better would be a method to take
>> > as input the output of an arbitrary SQL query. Ideas?
>> >
>>
>>
>> Hello,
>>
>> I realize this post is pretty old, but I was wondering if you found an
>> answer to this question and if you've used it.
>> I have to load data from SQL Server into Cassandra and I am completely new
>> to Cassandra and all of the posts I seem to be able to find are demos
>> about loading from MySQL into Cassandra.
>> Any, any help would be extremely appreciated!
>> Thank you very much!
>> Raluca
>>
>>
>>
>>
>>
>>
>
>
> --
> Jason Kushmaul | 517.899.7852
> Engineering Manager
>

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Jared Biel]

I assume "@ Of node" is ethX's IP address? Has cassandra been restarted
since changes were made to cassandra.yaml? The netstat output that you
posted doesn't look right; we use settings similar to what you've posted.
Here's what it looks like on one of our nodes.


-Jared

On 14 September 2015 at 10:34, Ahmed Eljami  wrote:

> In cassanrda.yaml:
> listen_address:@ Of node
> rpc_address:0.0.0.0
>
> brodcast_rpc_address:@ Of node
>
> 2015-09-14 11:31 GMT+01:00 Neha Dave :
>
>> Try
>> >cqlsh 
>>
>> regards
>> Neha
>>
>> On Mon, Sep 14, 2015 at 3:53 PM, Ajay Garg 
>> wrote:
>>
>>> Hi All.
>>>
>>> We have setup a Ubuntu-14.04 server, and followed the steps exactly as
>>> per http://wiki.apache.org/cassandra/DebianPackaging
>>>
>>> Installation completes fine, Cassandra starts fine, however cqlsh does
>>> not work.
>>> We get the error ::
>>>
>>>
>>> ###
>>> ajay@comp:~$ cqlsh
>>> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
>>> error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
>>> None")})
>>>
>>> ###
>>>
>>>
>>>
>>> Version-Info ::
>>>
>>>
>>> ###
>>> ajay@comp:~$ dpkg -l | grep cassandra
>>> ii  cassandra   2.1.9
>>>  all  distributed storage system for structured data
>>>
>>> ###
>>>
>>>
>>>
>>> The port "seems" to be opened fine.
>>>
>>>
>>> ###
>>> ajay@comp:~$ netstat -an | grep 9042
>>> tcp6   0  0 127.0.0.1:9042  :::*
>>> LISTEN
>>>
>>> ###
>>>
>>>
>>>
>>> Firewall-filters ::
>>>
>>>
>>> ###
>>> ajay@comp:~$ sudo iptables -L
>>> [sudo] password for ajay:
>>> Chain INPUT (policy ACCEPT)
>>> target prot opt source   destination
>>> ACCEPT all  --  anywhere anywhere state
>>> RELATED,ESTABLISHED
>>> ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
>>> DROP   all  --  anywhere anywhere
>>>
>>> Chain FORWARD (policy ACCEPT)
>>> target prot opt source   destination
>>>
>>> Chain OUTPUT (policy ACCEPT)
>>> target prot opt source   destination
>>>
>>> ###
>>>
>>>
>>>
>>> Even telnet fails :(
>>>
>>>
>>> ###
>>> ajay@comp:~$ telnet localhost 9042
>>> Trying 127.0.0.1...
>>>
>>> ###
>>>
>>>
>>>
>>> Any ideas please?? We have been stuck on this for a good 3 hours now :(
>>>
>>>
>>>
>>> Thanks and Regards,
>>> Ajay
>>>
>>
>>
>
>
> --
> Cordialement;
>
> Ahmed ELJAMI
>

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ajay Garg]

Hi All.

Thanks for your replies.

a)
cqlsh  does not work either :(


b)
Following are the parameters as asked ::

listen_address: localhost
rpc_address: localhost

broadcast_rpc_address is not set.
According to the yaml file ::

# RPC address to broadcast to drivers and other Cassandra nodes. This cannot
# be set to 0.0.0.0. If left blank, this will be set to the value of
# rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address must
# be set.
# broadcast_rpc_address: 1.2.3.4


c)
Following is the netstat-output, with process information ::

###
ajay@comp:~$ sudo netstat -apn | grep 9042
[sudo] password for admin:
tcp6   0  0 127.0.0.1:9042  :::*
LISTEN  10169/java
###


Kindly let me know what else we can try .. it is really driving us nuttsss :(

On Mon, Sep 14, 2015 at 9:40 PM, Jared Biel
 wrote:
> Whoops, I accidentally pressed a hotkey and sent my message prematurely.
> Here's what netstat should look like with those settings:
>
> sudo netstat -apn | grep 9042
> tcp6   0  0 0.0.0.0:9042:::*LISTEN
> 21248/java
>
> -Jared
>
> On 14 September 2015 at 16:09, Jared Biel 
> wrote:
>>
>> I assume "@ Of node" is ethX's IP address? Has cassandra been restarted
>> since changes were made to cassandra.yaml? The netstat output that you
>> posted doesn't look right; we use settings similar to what you've posted.
>> Here's what it looks like on one of our nodes.
>>
>>
>> -Jared
>>
>> On 14 September 2015 at 10:34, Ahmed Eljami 
>> wrote:
>>>
>>> In cassanrda.yaml:
>>> listen_address:@ Of node
>>> rpc_address:0.0.0.0
>>>
>>> brodcast_rpc_address:@ Of node
>>>
>>> 2015-09-14 11:31 GMT+01:00 Neha Dave :

 Try
 >cqlsh 

 regards
 Neha

 On Mon, Sep 14, 2015 at 3:53 PM, Ajay Garg 
 wrote:
>
> Hi All.
>
> We have setup a Ubuntu-14.04 server, and followed the steps exactly as
> per http://wiki.apache.org/cassandra/DebianPackaging
>
> Installation completes fine, Cassandra starts fine, however cqlsh does
> not work.
> We get the error ::
>
>
> ###
> ajay@comp:~$ cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
> None")})
>
> ###
>
>
>
> Version-Info ::
>
>
> ###
> ajay@comp:~$ dpkg -l | grep cassandra
> ii  cassandra   2.1.9
>  all  distributed storage system for structured data
>
> ###
>
>
>
> The port "seems" to be opened fine.
>
>
> ###
> ajay@comp:~$ netstat -an | grep 9042
> tcp6   0  0 127.0.0.1:9042  :::*
> LISTEN
>
> ###
>
>
>
> Firewall-filters ::
>
>
> ###
> ajay@comp:~$ sudo iptables -L
> [sudo] password for ajay:
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT tcp  --  anywhere anywhere tcp
> dpt:ssh
> DROP   all  --  anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
>
> ###
>
>
>
> Even telnet fails :(
>
>
> ###
> ajay@comp:~$ telnet localhost 9042
> Trying 127.0.0.1...
>
> ###
>
>
>
> Any ideas please?? We 

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Jared Biel]

Is there a reason that you're setting listen_address and rpc_address to
localhost?

listen_address doc: "the Right Thing is to use the address associated with
the hostname". So, set the IP address of this to eth0 for example. I
believe if it is set to localhost then you won't be able to form a cluster
with other nodes.

rpc_address: this is the address to which clients will connect. I recommend
0.0.0.0 here so clients can connect to IP address of the server as well as
localhost if they happen to reside on the same instance.


Here are all of the address settings from our config file. 192.168.1.10 is
the IP address of eth0 and broadcast_address is commented out.

listen_address: 192.168.1.10
# broadcast_address: 1.2.3.4
rpc_address: 0.0.0.0
broadcast_rpc_address: 192.168.1.10

Follow these directions to get up and running with the first node
(destructive process):

1. Stop cassandra
2. Remove data from cassandra var directory (rm -rf /var/lib/cassandra/*)
3. Make above changes to config file. Also set seeds to the eth0 IP address
4. Start cassandra
5. Set seeds in config file back to "" after cassandra is up and running.

After following that process, you'll be able to connect to the node from
any host that can reach Cassandra's ports on that node ("cqlsh" command
will work.) To join more nodes to the cluster, follow the steps same steps
as above, except the seeds value to the IP address of an already running
node.

Regarding the empty "seeds" config entry: our configs are automated with
configuration management. During the node bootstrap process a script
performs the above. The reason that we set seeds back to empty is that we
don't want nodes coming up/down to cause the config file to change and thus
cassandra to restart needlessly. So far we haven't had any issues with
seeds being set to empty after a node has joined the cluster, but this may
not be the recommended way of doing things.

-Jared

On 14 September 2015 at 16:46, Ajay Garg  wrote:

> Hi All.
>
> Thanks for your replies.
>
> a)
> cqlsh  does not work either :(
>
>
> b)
> Following are the parameters as asked ::
>
> listen_address: localhost
> rpc_address: localhost
>
> broadcast_rpc_address is not set.
> According to the yaml file ::
>
> # RPC address to broadcast to drivers and other Cassandra nodes. This
> cannot
> # be set to 0.0.0.0. If left blank, this will be set to the value of
> # rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address must
> # be set.
> # broadcast_rpc_address: 1.2.3.4
>
>
> c)
> Following is the netstat-output, with process information ::
>
>
> ###
> ajay@comp:~$ sudo netstat -apn | grep 9042
> [sudo] password for admin:
> tcp6   0  0 127.0.0.1:9042  :::*
> LISTEN  10169/java
>
> ###
>
>
> Kindly let me know what else we can try .. it is really driving us nuttsss
> :(
>
> On Mon, Sep 14, 2015 at 9:40 PM, Jared Biel
>  wrote:
> > Whoops, I accidentally pressed a hotkey and sent my message prematurely.
> > Here's what netstat should look like with those settings:
> >
> > sudo netstat -apn | grep 9042
> > tcp6   0  0 0.0.0.0:9042:::*
> LISTEN
> > 21248/java
> >
> > -Jared
> >
> > On 14 September 2015 at 16:09, Jared Biel  >
> > wrote:
> >>
> >> I assume "@ Of node" is ethX's IP address? Has cassandra been restarted
> >> since changes were made to cassandra.yaml? The netstat output that you
> >> posted doesn't look right; we use settings similar to what you've
> posted.
> >> Here's what it looks like on one of our nodes.
> >>
> >>
> >> -Jared
> >>
> >> On 14 September 2015 at 10:34, Ahmed Eljami 
> >> wrote:
> >>>
> >>> In cassanrda.yaml:
> >>> listen_address:@ Of node
> >>> rpc_address:0.0.0.0
> >>>
> >>> brodcast_rpc_address:@ Of node
> >>>
> >>> 2015-09-14 11:31 GMT+01:00 Neha Dave :
> 
>  Try
>  >cqlsh 
> 
>  regards
>  Neha
> 
>  On Mon, Sep 14, 2015 at 3:53 PM, Ajay Garg 
>  wrote:
> >
> > Hi All.
> >
> > We have setup a Ubuntu-14.04 server, and followed the steps exactly
> as
> > per http://wiki.apache.org/cassandra/DebianPackaging
> >
> > Installation completes fine, Cassandra starts fine, however cqlsh
> does
> > not work.
> > We get the error ::
> >
> >
> >
> ###
> > ajay@comp:~$ cqlsh
> > Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> > error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
> > None")})
> >
> >
> 

Re: Question: Gossip Protocol

[Nate McCall]

It is hard coded in Gossiper:
https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/gms/Gossiper.java#L83

What requirement are you trying to address by increasing this value?

On Mon, Sep 14, 2015 at 8:26 AM, Thouraya TH  wrote:

>  I find this information :
>
> The gossip process runs every second and exchanges state messages with up
> to three other nodes in the cluster.
>
> here
> http://docs.datastax.com/en/cassandra/2.0/cassandra/architecture/architectureGossipAbout_c.html
>
>
> Please, i ask if it is possible to change this periode, to three seconds ?
>
> Kind regards.
>
>
>
>
> 2015-09-14 14:15 GMT+01:00 Thouraya TH :
>
>> Hi all,
>>
>> Please, the gossip procotol in cassandra is running every ... seconds ?
>>
>>
>> Thank you so much for answers.
>> Best Regards.
>>
>
>


-- 
-
Nate McCall
Austin, TX
@zznate

Co-Founder & Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Upgrade Limitations Question

[Robert Coli]

On Wed, Sep 9, 2015 at 12:09 PM, Vasileios Vlachos <
vasileiosvlac...@gmail.com> wrote:

> In our case the restart bit has already been done. Do you know if it would
> be a bad idea to create a new KS before all nodes have upgraded their
> SSTables?
>

This particular case is probably fine. The reason for the caution against
issuing certain kinds of queries during a rolling restart is twofold :

1) TRUNCATE requires all known nodes to be available to succeed, if you are
restarting one, it won't be available.
2) in theory, the newly upgraded nodes might not get the DDL schema update
properly due to some incompatible change

To check for 2, do :
"
nodetool gossipinfo | grep SCHEMA |sort | uniq -c | sort -n
"

Before and after and make sure the schema propagates correctly. There
should be a new version on all nodes between each DDL change, if there is
you will likely be able to see the new schema on all the new nodes.

Test in a test environment with the specific versions before trying in
production.

=Rob

Re: cassandra-stress on 3.0 with column widths benchmark.

[Nate McCall]

By default, stress runs stop after throughput has not improved after three
runs. This functionality is a little difficult to figure out from the
documentation, so take a look at (maybe even with a debugger attached):
https://github.com/apache/cassandra/blob/cassandra-2.1/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L111
to see what's going on.

In both scenarios, this may have taken roughly the same time to hit
saturation, but for different reasons and with different results as you
saw.

To really find out why, it would be a good idea to enable one of the
reporters (
http://www.datastax.com/dev/blog/pluggable-metrics-reporting-in-cassandra-2-0-2)
to send cluster metrics to a monitoring system such as Graphite. At the
very least get OpsCenter running and capturing metrics from the cluster.
Either way, getting familiar with a visual picture of the runtime now is
invaluable for really understanding any future production deployment.

On Sun, Sep 13, 2015 at 9:25 PM, Kevin Burton  wrote:

> I’m trying to benchmark two scenarios…
>
> 10 columns with 150 bytes each
>
> vs
>
> 150 columns with 10 bytes each.
>
> The total row “size” would be 1500 bytes (ignoring overhead).
>
> Our app uses 150 columns so I’m trying to see if packing it into a JSON
> structure using one column would improve performance.
>
> I seem to have confirmed my hypothesis.
>
> I’m running two tests:
>
> ./tools/bin/cassandra-stress write -insert -col n=FIXED\(10\)
>> size=FIXED\(150\) | tee cassandra-stress-10-150.log
>>
>
>
>> time ./tools/bin/cassandra-stress write -insert -col n=FIXED\(150\)
>> size=FIXED\(10\) | tee cassandra-stress-150-10.log
>
>
> this shows that the "op rate” is much much lower when running with 150
> columns:
>
> root@util0063 ~/apache-cassandra-3.0.0-beta2 # grep "op rate"
>> cassandra-stress-10-150.log
>> op rate   : 7632 [WRITE:7632]
>> op rate   : 11851 [WRITE:11851]
>> op rate   : 31967 [WRITE:31967]
>> op rate   : 41798 [WRITE:41798]
>> op rate   : 51251 [WRITE:51251]
>> op rate   : 58057 [WRITE:58057]
>> op rate   : 62977 [WRITE:62977]
>> op rate   : 65398 [WRITE:65398]
>> op rate   : 67673 [WRITE:67673]
>> op rate   : 69198 [WRITE:69198]
>> op rate   : 70402 [WRITE:70402]
>> op rate   : 71019 [WRITE:71019]
>> op rate   : 71574 [WRITE:71574]
>> root@util0063 ~/apache-cassandra-3.0.0-beta2 # grep "op rate"
>> cassandra-stress-150-10.log
>> op rate   : 2570 [WRITE:2570]
>> op rate   : 5144 [WRITE:5144]
>> op rate   : 10906 [WRITE:10906]
>> op rate   : 11832 [WRITE:11832]
>> op rate   : 12471 [WRITE:12471]
>> op rate   : 12915 [WRITE:12915]
>> op rate   : 13620 [WRITE:13620]
>> op rate   : 13456 [WRITE:13456]
>> op rate   : 13916 [WRITE:13916]
>> op rate   : 14029 [WRITE:14029]
>> op rate   : 13915 [WRITE:13915]
>
>
> … what’s WEIRD here is that
>
> Both tests take about 10 minutes.  Yet it’s saying that the op rate for
> the second is slower.  Why would that be? That doesn’t make much sense…
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> 
>
>


-- 
-
Nate McCall
Austin, TX
@zznate

Co-Founder & Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ajay Garg]

Hi All.

I re-established my server from scratch, and installed the 21x server.
Now, cqlsh works right out of the box.

When I had last setup the server, I had (accidentally) installed the
20x server on first attempt, removed it, and then installed the 21x
series server. Seems that caused some hidden problem.


I am heartfully grateful to everyone for bearing with me.


Thanks and Regards,
Ajay

On Tue, Sep 15, 2015 at 10:16 AM, Ajay Garg  wrote:
> Hi Jared.
>
> Thanks for your help.
>
> I made the config-changes.
> Also, I changed the seed (right now, we are just trying to get one
> instance up and running) ::
>
> 
> seed_provider:
> # Addresses of hosts that are deemed contact points.
> # Cassandra nodes use this list of hosts to find each other and learn
> # the topology of the ring.  You must change this if you are running
> # multiple nodes!
> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>   parameters:
>   # seeds is actually a comma-delimited list of addresses.
>   # Ex: ",,"
>   - seeds: "our.ip.address.here"
> 
>
>
>
>
> Following is the netstat output ::
>
> 
> ajay@comp:~$ sudo netstat -apn | grep 9042
> tcp6   0  0 0.0.0.0:9042:::*
> LISTEN  22469/java
> 
>
>
>
> Still, when I try, we get ::
>
> 
> ajay@comp:~$ cqlsh our.ip.address.here
> Connection error: ('Unable to connect to any servers',
> {'our.ip.address.here': error(None, "Tried connecting to
> [('our.ip.address.here', 9042)]. Last error: None")})
> 
>
>
> :( :(
>
> On Mon, Sep 14, 2015 at 11:00 PM, Jared Biel
>  wrote:
>> Is there a reason that you're setting listen_address and rpc_address to
>> localhost?
>>
>> listen_address doc: "the Right Thing is to use the address associated with
>> the hostname". So, set the IP address of this to eth0 for example. I believe
>> if it is set to localhost then you won't be able to form a cluster with
>> other nodes.
>>
>> rpc_address: this is the address to which clients will connect. I recommend
>> 0.0.0.0 here so clients can connect to IP address of the server as well as
>> localhost if they happen to reside on the same instance.
>>
>>
>> Here are all of the address settings from our config file. 192.168.1.10 is
>> the IP address of eth0 and broadcast_address is commented out.
>>
>> listen_address: 192.168.1.10
>> # broadcast_address: 1.2.3.4
>> rpc_address: 0.0.0.0
>> broadcast_rpc_address: 192.168.1.10
>>
>> Follow these directions to get up and running with the first node
>> (destructive process):
>>
>> 1. Stop cassandra
>> 2. Remove data from cassandra var directory (rm -rf /var/lib/cassandra/*)
>> 3. Make above changes to config file. Also set seeds to the eth0 IP address
>> 4. Start cassandra
>> 5. Set seeds in config file back to "" after cassandra is up and running.
>>
>> After following that process, you'll be able to connect to the node from any
>> host that can reach Cassandra's ports on that node ("cqlsh" command will
>> work.) To join more nodes to the cluster, follow the steps same steps as
>> above, except the seeds value to the IP address of an already running node.
>>
>> Regarding the empty "seeds" config entry: our configs are automated with
>> configuration management. During the node bootstrap process a script
>> performs the above. The reason that we set seeds back to empty is that we
>> don't want nodes coming up/down to cause the config file to change and thus
>> cassandra to restart needlessly. So far we haven't had any issues with seeds
>> being set to empty after a node has joined the cluster, but this may not be
>> the recommended way of doing things.
>>
>> -Jared
>>
>> On 14 September 2015 at 16:46, Ajay Garg  wrote:
>>>
>>> Hi All.
>>>
>>> Thanks for your replies.
>>>
>>> a)
>>> cqlsh  does not work either :(
>>>
>>>
>>> b)
>>> Following are the parameters as asked ::
>>>
>>> listen_address: localhost
>>> rpc_address: localhost
>>>
>>> broadcast_rpc_address is not set.
>>> According to the yaml file ::
>>>
>>> # RPC address to broadcast to drivers and other Cassandra nodes. This
>>> cannot
>>> # be set to 0.0.0.0. If left blank, this will be set to the value of
>>> # rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address
>>> must
>>> # be set.
>>> # broadcast_rpc_address: 1.2.3.4
>>>
>>>
>>> c)
>>> Following is the netstat-output, with process information ::
>>>
>>>
>>> ###
>>> ajay@comp:~$ sudo netstat -apn | 

Seeing null pointer exception 2.0.14 after purging gossip state

[K F]

Hi,
I have cassandra 2.0.14 deployed and after following the method described in 
Apache Cassandra™ 2.0 to clear the gossip state of the node in one of the dc of 
my cluster
|   |
|   |   |   |   |   |
| Apache Cassandra™ 2.0Correcting a problem in the gossip state. | Version 2.0 |
|  |
| View on docs.datastax.com | Preview by Yahoo |
|  |
|   |

 I see wierd exception on the nodes not many but a few in an hour for nodes 
that have already successfully decommissioned from the cluster, you can see 
from below exception that 10.0.0.1 has been already decommissioned. Below is 
the exception snippet. 
Has anyone observed a similar behaviour? e.g. 10.0.0.1 is decommissioned
Is this a bug in cassandra 2.0.x?
2015-09-15 02:35:14,056 [GossipStage:9] INFO Gossiper InetAddress /10.0.0.1 is 
now DOWN2015-09-15 02:35:14,058 [GossipStage:9] INFO StorageService Removing 
tokens [15950735949418990474845684723364134913] for /10.0.0.1
2015-09-15 02:35:14,061 [GossipStage:9] ERROR CassandraDaemon Exception in 
thread Thread[GossipStage:9,5,main]java.lang.NullPointerException at 
org.apache.cassandra.service.StorageService.getRpcaddress(StorageService.java:1067)
 at 
org.apache.cassandra.transport.Server$EventNotifier.getRpcAddress(Server.java:345)
 at 
org.apache.cassandra.transport.Server$EventNotifier.onLeaveCluster(Server.java:366)
 at 
org.apache.cassandra.service.StorageService.excise(StorageService.java:1790) at 
org.apache.cassandra.service.StorageService.excise(StorageService.java:1798) at 
org.apache.cassandra.service.StorageService.handleStateLeft(StorageService.java:1701)
 at 
org.apache.cassandra.service.StorageService.onChange(StorageService.java:1361) 
at org.apache.cassandra.service.StorageService.onJoin(StorageService.java:1995) 
at org.apache.cassandra.gms.Gossiper.handleMajorStateChange(Gossiper.java:1003) 
at org.apache.cassandra.gms.Gossiper.applyStateLocally(Gossiper.java:1102) at 
org.apache.cassandra.gms.GossipDigestAck2VerbHandler.doVerb(GossipDigestAck2VerbHandler.java:49)
 at 
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:62) 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:745)

Re: Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ajay Garg]

Hi Jared.

Thanks for your help.

I made the config-changes.
Also, I changed the seed (right now, we are just trying to get one
instance up and running) ::


seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring.  You must change this if you are running
# multiple nodes!
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
  parameters:
  # seeds is actually a comma-delimited list of addresses.
  # Ex: ",,"
  - seeds: "our.ip.address.here"





Following is the netstat output ::


ajay@comp:~$ sudo netstat -apn | grep 9042
tcp6   0  0 0.0.0.0:9042:::*
LISTEN  22469/java




Still, when I try, we get ::


ajay@comp:~$ cqlsh our.ip.address.here
Connection error: ('Unable to connect to any servers',
{'our.ip.address.here': error(None, "Tried connecting to
[('our.ip.address.here', 9042)]. Last error: None")})



:( :(

On Mon, Sep 14, 2015 at 11:00 PM, Jared Biel
 wrote:
> Is there a reason that you're setting listen_address and rpc_address to
> localhost?
>
> listen_address doc: "the Right Thing is to use the address associated with
> the hostname". So, set the IP address of this to eth0 for example. I believe
> if it is set to localhost then you won't be able to form a cluster with
> other nodes.
>
> rpc_address: this is the address to which clients will connect. I recommend
> 0.0.0.0 here so clients can connect to IP address of the server as well as
> localhost if they happen to reside on the same instance.
>
>
> Here are all of the address settings from our config file. 192.168.1.10 is
> the IP address of eth0 and broadcast_address is commented out.
>
> listen_address: 192.168.1.10
> # broadcast_address: 1.2.3.4
> rpc_address: 0.0.0.0
> broadcast_rpc_address: 192.168.1.10
>
> Follow these directions to get up and running with the first node
> (destructive process):
>
> 1. Stop cassandra
> 2. Remove data from cassandra var directory (rm -rf /var/lib/cassandra/*)
> 3. Make above changes to config file. Also set seeds to the eth0 IP address
> 4. Start cassandra
> 5. Set seeds in config file back to "" after cassandra is up and running.
>
> After following that process, you'll be able to connect to the node from any
> host that can reach Cassandra's ports on that node ("cqlsh" command will
> work.) To join more nodes to the cluster, follow the steps same steps as
> above, except the seeds value to the IP address of an already running node.
>
> Regarding the empty "seeds" config entry: our configs are automated with
> configuration management. During the node bootstrap process a script
> performs the above. The reason that we set seeds back to empty is that we
> don't want nodes coming up/down to cause the config file to change and thus
> cassandra to restart needlessly. So far we haven't had any issues with seeds
> being set to empty after a node has joined the cluster, but this may not be
> the recommended way of doing things.
>
> -Jared
>
> On 14 September 2015 at 16:46, Ajay Garg  wrote:
>>
>> Hi All.
>>
>> Thanks for your replies.
>>
>> a)
>> cqlsh  does not work either :(
>>
>>
>> b)
>> Following are the parameters as asked ::
>>
>> listen_address: localhost
>> rpc_address: localhost
>>
>> broadcast_rpc_address is not set.
>> According to the yaml file ::
>>
>> # RPC address to broadcast to drivers and other Cassandra nodes. This
>> cannot
>> # be set to 0.0.0.0. If left blank, this will be set to the value of
>> # rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address
>> must
>> # be set.
>> # broadcast_rpc_address: 1.2.3.4
>>
>>
>> c)
>> Following is the netstat-output, with process information ::
>>
>>
>> ###
>> ajay@comp:~$ sudo netstat -apn | grep 9042
>> [sudo] password for admin:
>> tcp6   0  0 127.0.0.1:9042  :::*
>> LISTEN  10169/java
>>
>> ###
>>
>>
>> Kindly let me know what else we can try .. it is really driving us nuttsss
>> :(
>>
>> On Mon, Sep 14, 2015 at 9:40 PM, Jared Biel
>>  wrote:
>> > Whoops, I accidentally pressed a hotkey and sent my message prematurely.
>> > Here's what netstat should look like with those settings:
>> >
>> > sudo netstat -apn | grep 9042
>> > tcp6   0  0 0.0.0.0:9042   

Re: Question: Gossip Protocol

[Robert Coli]

On Mon, Sep 14, 2015 at 6:26 AM, Thouraya TH  wrote:

> Please, i ask if it is possible to change this periode, to three seconds ?
>

It's an unusual question to ask; in return I must ask "why do you want to
change the gossip period?"

The answer is "yes, if you are willing to recompile" :

cassandra/src/java/org/apache/cassandra/gms/Gossiper.java
"
public final static int intervalInMillis = 1000;
"

Change this to 3000.

=Rob

LTCS Strategy Resulting in multiple SSTables

[Saladi Naidu]

We are using Level Tiered Compaction Strategy on a Column Family. Below are 
CFSTATS from two nodes in same cluster, one node has 880 SStables in L0 whereas 
one node just has 1 SSTable in L0. In the node where there are multiple 
SStables, all of them are small size and created same time stamp. We ran 
Compaction, it did not result in much change, node remained with huge number of 
SStables. Due to this large number of SSTables, Read performance is being 
impacted
In same cluster, under same keyspace, we are observing this discrepancy in 
other column families as well. What is going wrong? What is the solution to fix 
this
---NODE1---

   Table: category_ranking_dedup

   SSTable count: 1

   SSTables in each level: [1, 0, 0, 0, 0, 0, 0, 0, 
0]

   Space used (live): 2012037

   Space used (total): 2012037

   Space used by snapshots (total): 0

   SSTable Compression Ratio: 0.07677216119569073

   Memtable cell count: 990

   Memtable data size: 32082

   Memtable switch count: 11

   Local read count: 2842

   Local read latency: 3.215 ms

   Local write count: 18309

   Local write latency: 5.008 ms

   Pending flushes: 0

   Bloom filter false positives: 0

   Bloom filter false ratio: 0.0

   Bloom filter space used: 816

   Compacted partition minimum bytes: 87

   Compacted partition maximum bytes: 25109160

   Compacted partition mean bytes: 22844

   Average live cells per slice (last five 
minutes): 338.84588318085855

   Maximum live cells per slice (last five 
minutes): 10002.0

   Average tombstones per slice (last five 
minutes): 36.53307529908515

   Maximum tombstones per slice (last five 
minutes): 36895.0

 NODE2---  

Table: category_ranking_dedup

   SSTable count: 808

   SSTables in each level: [808/4, 0, 0, 0, 0, 0, 
0, 0, 0]

   Space used (live): 291641980

   Space used (total): 291641980

   Space used by snapshots (total): 0

   SSTable Compression Ratio: 0.1431106696818256

   Memtable cell count: 4365293

   Memtable data size: 3742375

   Memtable switch count: 44

   Local read count: 2061

   Local read latency: 31.983 ms

   Local write count: 30096

   Local write latency: 27.449 ms

   Pending flushes: 0

   Bloom filter false positives: 0

   Bloom filter false ratio: 0.0

   Bloom filter space used: 54544

   Compacted partition minimum bytes: 87

   Compacted partition maximum bytes: 25109160

   Compacted partition mean bytes: 634491

   Average live cells per slice (last five 
minutes): 416.1780688985929

   Maximum live cells per slice (last five 
minutes): 10002.0

   Average tombstones per slice (last five 
minutes): 45.11547792333818

   Maximum tombstones per slice (last five 
minutes): 36895.0




 Naidu Saladi 

Possible to restore ENTIRE data from Cassandra-Schema in one go?

[Ajay Garg]

Hi All.

We have a schema on one Cassandra-node, and wish to duplicate the
entire schema on another server.
Think of this a 2 clusters, each cluster containing one node.

We have found the way to dump/restore schema-metainfo at ::

https://dzone.com/articles/dumpingloading-schema


And dumping/restoring data at ::

http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_backup_takes_snapshot_t.html
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_backup_snapshot_restore_t.html


For the restoring data step, it seems that restoring every "table"
requires a dedicated step.
So, if the schema has 100 "tables", we would need 100 steps.


Is it so? If yes, can the entire data be dumped/restored in one go?
Just asking, to save time, if it could :)




Thanks and Regards,
Ajay

Extremely high CPU load in new data center

[Tom van den Berge]

I have a DC of 4 nodes that must be expanded to accommodate an expected
growth in data. Since the DC is not using vnodes, we have decided to set up
a new DC with vnodes enabled, start using the new DC, and decommission the
old DC.

Both DCs have 4 nodes. The idea is to add additional nodes to the new DC
later on.
The servers in both DCs are very similar: quad-core machines with 8GB.

We have bootstrapped/rebuilt the nodes in the new DC. When that finished,
the nodes in the new DC were showing little CPU activity, as you would
expect, because they are receiving writes from the other DC. So far, so
good.

Then we switched the clients from the old DC to the new DC. The CPU load on
all nodes in the new DC immediately rose to excessively high levels (15 -
25), which made the servers effectively unavailable. The load did not drop
structurally within 20 minutes, so we had to switch the clients back to the
old DC. Then the load dropped again.

What can be the reason for the high CPU loads on the new nodes?

Performance test shows that the servers in the new DC perform slightly
better (both IO and CPU) than the servers in the old DC.
I did not see anything abnormal in the Cassandra logs, like garbage
collection warnings. I also did not see any strange things in the tpstats.
The only difference I'm aware of between the old and new DC is the use of
vnodes.

Any help is appreciated!
Thanks,
Tom

Re: Best strategy for hiring from OSS communities.

[Alain RODRIGUEZ]

Hi Kevin,

You can try --> https://twitter.com/Cassandra_Jobs

Anyway, I saw your message and I imagine other people looking for a job
right know did as well already.
You can also try to spot people through Linkedin, a few companies contacted
me that way too, it might work for you.

Then you can also try to be present at some events or say you're recruiting
on your technical blog, alongside your most interesting article about
Cassandra ;-).

Hope any of these helped.

Alain

2015-09-14 1:18 GMT+02:00 Kevin Burton :

> I think j...@apache.org is dead…
>
> I saw this:
>
>
> http://mail-archives.apache.org/mod_mbox/community-dev/201304.mbox/%3CCAKQbXgAgO_3SzLMR0L4p_qkSALQzE=ehpnbmjndccu6dtm-...@mail.gmail.com%3E
>
> And can’t find any documentation on a j...@apache.org
>
> I think it would be valuable to create one.  Maybe I should post to
> general@ …
>
> On Fri, Sep 11, 2015 at 5:34 PM, Otis Gospodnetić <
> otis.gospodne...@gmail.com> wrote:
>
>> Hey Kevin - I think there is j...@apache.org
>>
>> Otis
>> --
>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>> Solr & Elasticsearch Support * http://sematext.com/
>>
>>
>> On Thu, Aug 13, 2015 at 6:02 PM, Kevin Burton  wrote:
>>
>>> Mildly off topic but we are looking to hire someone with Cassandra
>>> experience..
>>>
>>> I don’t necessarily want to spam the list though.  We’d like someone
>>> from the community who contributes to Open Source, etc.
>>>
>>> Are there forums for Apache / Cassandra, etc for jobs? I couldn’t fine
>>> one.
>>>
>>> --
>>>
>>> Founder/CEO Spinn3r.com
>>> Location: *San Francisco, CA*
>>> blog: http://burtonator.wordpress.com
>>> … or check out my Google+ profile
>>> 
>>>
>>>
>>
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> 
>
>

Test Subject

[Ajay Garg]

Testing simple content, as my previous email bounced :(

-- 
Regards,
Ajay

Not able to cqlsh on 2.1.9 on Ubuntu 14.04

[Ajay Garg]

Hi All.

We have setup a Ubuntu-14.04 server, and followed the steps exactly as
per http://wiki.apache.org/cassandra/DebianPackaging

Installation completes fine, Cassandra starts fine, however cqlsh does not work.
We get the error ::

###
ajay@comp:~$ cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1':
error(None, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
None")})
###



Version-Info ::

###
ajay@comp:~$ dpkg -l | grep cassandra
ii  cassandra   2.1.9
 all  distributed storage system for structured data
###



The port "seems" to be opened fine.

###
ajay@comp:~$ netstat -an | grep 9042
tcp6   0  0 127.0.0.1:9042  :::*LISTEN
###



Firewall-filters ::

###
ajay@comp:~$ sudo iptables -L
[sudo] password for ajay:
Chain INPUT (policy ACCEPT)
target prot opt source   destination
ACCEPT all  --  anywhere anywhere state
RELATED,ESTABLISHED
ACCEPT tcp  --  anywhere anywhere tcp dpt:ssh
DROP   all  --  anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
###



Even telnet fails :(

###
ajay@comp:~$ telnet localhost 9042
Trying 127.0.0.1...
###



Any ideas please?? We have been stuck on this for a good 3 hours now :(



Thanks and Regards,
Ajay