CQLSH is not connecting - Trunk Version

2014-11-11 Thread Rajanarayanan Thottuvaikkatumana
In the trunk version of the code base with the latest code, the cqlsh is not 
connecting. Here is the message I am getting.

Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ ./bin/cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
ConnectionShutdown('Connection  is already closed',)})

I have done restarting to make sure that there is no clash with the port number 
and stuff like that. The server has started without any exceptions.

Any idea?

Thanks
-Raj

Re: CQLSH is not connecting - Trunk Version

2014-11-11 Thread Rajanarayanan Thottuvaikkatumana
If I give the explicit host address and port number, it connects. So by default 
it takes the thrift service port and in my opinion that is not a correct 
behavior.

Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ ./bin/cqlsh 127.0.0.1 9042
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.0.0-SNAPSHOT | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh> 

Thanks
-Raj
On 11-Nov-2014, at 2:46 pm, Rajanarayanan Thottuvaikkatumana 
 wrote:

> In the trunk version of the code base with the latest code, the cqlsh is not 
> connecting. Here is the message I am getting.
> 
> Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ ./bin/cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
> ConnectionShutdown('Connection  (closed)> is already closed',)})
> 
> I have done restarting to make sure that there is no clash with the port 
> number and stuff like that. The server has started without any exceptions.
> 
> Any idea?
> 
> Thanks
> -Raj



Re: CQLSH is not connecting - Trunk Version

2014-11-11 Thread Aleksey Yeschenko
First, no, it does not by default connect to the thrift service port - it does 
use 9042 by default.

You most likely have the port overridden in ~/.cassandra/cqlshrc, set to 9160.

Secondly, this is not a question for dev@ - this belongs to the users mailing 
list.

Thanks.

-- 
AY

On November 11, 2014 at 5:53:04 PM, Rajanarayanan Thottuvaikkatumana 
(rnambood...@gmail.com) wrote:

If I give the explicit host address and port number, it connects. So by default 
it takes the thrift service port and in my opinion that is not a correct 
behavior.  

Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ ./bin/cqlsh 127.0.0.1 9042  
Connected to Test Cluster at 127.0.0.1:9042.  
[cqlsh 5.0.1 | Cassandra 3.0.0-SNAPSHOT | CQL spec 3.2.0 | Native protocol v3]  
Use HELP for help.  
cqlsh>  

Thanks  
-Raj  
On 11-Nov-2014, at 2:46 pm, Rajanarayanan Thottuvaikkatumana 
 wrote:  

> In the trunk version of the code base with the latest code, the cqlsh is not 
> connecting. Here is the message I am getting.  
>  
> Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ ./bin/cqlsh  
> Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
> ConnectionShutdown('Connection  (closed)> is already closed',)})  
>  
> I have done restarting to make sure that there is no clash with the port 
> number and stuff like that. The server has started without any exceptions.  
>  
> Any idea?  
>  
> Thanks  
> -Raj  



Reviewing patches

2014-11-11 Thread oded peer
I submitted patches for Cassandra-7304 (a month ago) and for Cassandra-4476
(a week ago).
Both patches are waiting to be reviewed.
These are my first patches in the Cassandra project.
Can anyone explain and how the review process works?
How long does it usually take for patches to be reviewed?

Thanks,
Oded


Debian mirror is blocked

2014-11-11 Thread Adam Israel
I recently filed a bug [1] about broken mirrors and debian repo for Cassandra. 
The mirror issue has been resolved, but there is still an issue with the Debian 
repo that is unresolved. The Infra team has blocked the debian repo because it 
was causing in excess of 600,000 requests/day.

The Debian packaging page [2] includes instructions on using the ASF 
repositories, which is what has been blocked. The ASF repo is listed 
predominantly on the page, even though it’s listed as an alternate to using the 
DataStax repo. 

What’s not entirely clear about the DataStax repo is if the packages its 
hosting are the same as the ones made available by the Cassandra team.

I stumbled across this while working on the Juju charm [3] that manages cloud 
deployments of Cassandra.

So the issues right now are that:
1) The Debian repo hosted on ASF is currently blocked
2) It’s unclear if the ASF or DataStax repo is authoritative
3) Upstream projects that depend on the ASF repo are currently broke.



[1] https://issues.apache.org/jira/browse/INFRA-8585
[2] http://wiki.apache.org/cassandra/DebianPackaging
[3] https://jujucharms.com/cassandra/precise/16

Thanks!
-- 
Adam Israel



Re: Debian mirror is blocked

2014-11-11 Thread Eric Evans
[ Adam Israel ]
> I recently filed a bug [1] about broken mirrors and debian repo for 
> Cassandra. The mirror issue has been resolved, but there is still an issue 
> with the Debian repo that is unresolved. The Infra team has blocked the 
> debian repo because it was causing in excess of 600,000 requests/day.

Interesting, I can see from the issue that INFRA claims to have blocked it,
but I am able to access it fine.  The source package for 2.1.2 is broken
at the moment (the orig.tar.gz 404s), but that's not because it's blocked.
 
> The Debian packaging page [2] includes instructions on using the ASF 
> repositories, which is what has been blocked. The ASF repo is listed 
> predominantly on the page, even though it’s listed as an alternate to using 
> the DataStax repo. 

Yes, the canonical download location for all ASF projects is supposed to
be from ASF resources. 

> What’s not entirely clear about the DataStax repo is if the packages its 
> hosting are the same as the ones made available by the Cassandra team.

I'm not sure, I assume at the very least that it's a different build to
that produced by the Cassandra Release Manager.  Either way, you shouldn't
consider it the Official Apache Cassandra Download(tm).

> I stumbled across this while working on the Juju charm [3] that manages cloud 
> deployments of Cassandra.
> 
> So the issues right now are that:
> 1) The Debian repo hosted on ASF is currently blocked
> 2) It’s unclear if the ASF or DataStax repo is authoritative
> 3) Upstream projects that depend on the ASF repo are currently broke.

Sorry, we'll get it sorted out.  Thanks for the heads up!

-- 
Eric Evans
eev...@sym-link.com


Re: Debian mirror is blocked

2014-11-11 Thread Eric Evans
[ Eric Evans ]
> [ Adam Israel ]
> > I recently filed a bug [1] about broken mirrors and debian repo for 
> > Cassandra. The mirror issue has been resolved, but there is still an issue 
> > with the Debian repo that is unresolved. The Infra team has blocked the 
> > debian repo because it was causing in excess of 600,000 requests/day.
> 
> Interesting, I can see from the issue that INFRA claims to have blocked it,
> but I am able to access it fine.  The source package for 2.1.2 is broken
> at the moment (the orig.tar.gz 404s), but that's not because it's blocked.
>  
> > The Debian packaging page [2] includes instructions on using the ASF 
> > repositories, which is what has been blocked. The ASF repo is listed 
> > predominantly on the page, even though it’s listed as an alternate to using 
> > the DataStax repo. 
> 
> Yes, the canonical download location for all ASF projects is supposed to
> be from ASF resources. 
> 
> > What’s not entirely clear about the DataStax repo is if the packages its 
> > hosting are the same as the ones made available by the Cassandra team.
> 
> I'm not sure, I assume at the very least that it's a different build to
> that produced by the Cassandra Release Manager.  Either way, you shouldn't
> consider it the Official Apache Cassandra Download(tm).
> 
> > I stumbled across this while working on the Juju charm [3] that manages 
> > cloud deployments of Cassandra.
> > 
> > So the issues right now are that:
> > 1) The Debian repo hosted on ASF is currently blocked
> > 2) It’s unclear if the ASF or DataStax repo is authoritative
> > 3) Upstream projects that depend on the ASF repo are currently broke.
> 
> Sorry, we'll get it sorted out.  Thanks for the heads up!

INFRA-8585 has been updated.

TL;DR The repository should be working (it is working for me), so keep us
in the loop if you continue to have problems.

Long term we need to find an alternative to hosting on www, but for the
meantime, INFRA is not supposed to be blocking access.

Cheers,


[*]: https://issues.apache.org/jira/browse/INFRA-8585


-- 
Eric Evans
eev...@sym-link.com