Re: Problems with cassandra on AWS

[Alain RODRIGUEZ]

Hi Kant.

it looks like ec2 instances cannot talk to each other using public IP's


"talk to each other" --> port 7000 (if not using ssl, 7001 if using it).
Make sure this port is open. From IP_1: telnet ip_2 7000 will tell you if
the port is opened.

"using public IP's" --> Are you using Ec2Snitch or Ec2MultiRegionSnitch.
The former uses exclusively private IP (listen_address, rpc_address and
broadcast_address empty / commented). The latter uses public ip for
broadcast_address. You need then to make sure ports are open between the
private IPs.

Having a look at 'nodetool status' before running operations should help
you determine the current status for your cluster. Nodes should be showing
UN status (Up, Normal).

C*heers,
---
Alain Rodriguez - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-07-11 10:02 GMT+02:00 Riccardo Ferrari :

> I would check your security group settings, you need to allow
> communication on cassandra ports (ie 9042,...)
>
> On Mon, Jul 11, 2016 at 8:17 AM, daemeon reiydelle 
> wrote:
>
>> xWell, I seem to recall that the private IP's are valid for
>> communications WITHIN one VPC. I assume you can log into one machine and
>> ping (or ssh) the others. If so, check that cassandra.yaml is not set to
>> listen on 127.0.0.1 (localhost).
>>
>>
>> *...*
>>
>>
>>
>> *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198
>> <%28%2B1%29%20415.501.0198>London (+44) (0) 20 8144 9872
>> <%28%2B44%29%20%280%29%2020%208144%209872>*
>>
>> On Sun, Jul 10, 2016 at 4:54 PM, Kant Kodali  wrote:
>>
>>> Hi Guys,
>>>
>>> I installed a 3 node Cassandra cluster on AWS and my replication factor
>>> is
>>> 3. I am trying to insert some data into a table. I set the consistency
>>> level of QUORUM at a Cassandra Session level. It only inserts into one
>>> node
>>> and unable to talk to other nodes because it is trying to contact other
>>> nodes through private IP and obviously that is failing so I am not sure
>>> how
>>> to change settings in say cassandra.yaml or somewhere such that
>>> rpc_address
>>> in system.peers table is updated to public IP's? I tried changing the
>>> seeds
>>> to all public IP's that didn't work as it looks like ec2 instances cannot
>>> talk to each other using public IP's. any help would be appreciated!
>>>
>>> Thanks,
>>> kant
>>>
>>
>>
>

Compaction strategy contribution

[Pedro Gordo]

Hi all

I'm finishing an MSc in which my final project is to implement a new
compaction strategy in Cassandra. I've discussed the main points of the
strategy with other community members and received valuable feedback.
However, I understand this will be a tough challenge for someone who has
never worked with Cassandra, but after getting to know the technology, I've
found it fascinating. This mixed with always wanting to contribute to an
ope source project led me to chose it as the topic for my MSC Project.

But because this is my first time contributing to an open source project,
I've some questions on how to proceed correctly. Looking at the Contribute
 page, I see that we're
supposed to create a ticket before starting working on it, so should I just
create one or does the strategy usefulness need to be validated by someone
before? In this case, should I just proceed and implement it, or do
something else? And finally, is this the correct mailing list to be asking
this sort of questions? :)

As for the code itself, in case I have a question like "Should we be using
an abstract class for compaction classes?" or "What is this method supposed
to do?", can I ask here?
What is the best course of action to learn about the details of the code in
Cassandra? I already saw that it has some comments, but probably won't be
enough for me.

The strategy I have in mind will be very simple until I finish the MSc.
After that, I'll improve it with other features and feedback I got, but for
the moment, it'll rely on a time interval (probably scheduled at specific
hours, maybe during a time with less traffic on the system). During that
time interval, the rows will be made unique across all SSTables, but only
if, after a prior analysis, we find that the row exists in a certain number
of SSTables above a certain threshold.

I suppose it's a naive strategy, but the aim here is to give me experience
with C*, and of course I'll be happy to take suggestions. But I'll probably
only use the ideas after delivering the project because, at the moment, I
need to keep it simple. Otherwise, I'll never be able to deliver the
project. :)

Sorry for the long email, and thanks for all the help in advance! I'm very
excited about this project and look forward to being part of this
community!

Best regards
Pedro Gordo

Re: 3.0.8 tag

[Michael Shuler]

On 07/11/2016 02:40 AM, Vlad wrote:
> 
> I see 3.0.8 tag (8b21d9) at
> https://git1-us-west.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/cassandra-3.0.8
> but not on https://github.com/apache/cassandra/commits/cassandra-3.0 

Tag mirroring to github is sometimes a little slow, but it's there.

¯\_(ツ)_/¯

https://github.com/apache/cassandra/tree/cassandra-3.0.8

-- 
Kind regards,
Michael

3.0.8 tag

[Vlad]

Hi,
I've pulled latest changes from 
http://git-wip-us.apache.org/repos/asf/cassandra.git but can't see 
cassandra-3.0.8 tag (commit 8b21d9e9e975ea07023ae6ec4c04d997006c1a0a) in Git.
And tag 3.0.8-tentattive (removed now) was 
1cff5faea1766fb874d1e68bbb18e222c522c0a6 

I see 3.0.8 tag (8b21d9) at 
https://git1-us-west.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/cassandra-3.0.8
   but not on https://github.com/apache/cassandra/commits/cassandra-3.0
Regards.

Re: Problems with cassandra on AWS

[daemeon reiydelle]

xWell, I seem to recall that the private IP's are valid for communications
WITHIN one VPC. I assume you can log into one machine and ping (or ssh) the
others. If so, check that cassandra.yaml is not set to listen on 127.0.0.1
(localhost).


*...*



*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198
<%28%2B1%29%20415.501.0198>London (+44) (0) 20 8144 9872
<%28%2B44%29%20%280%29%2020%208144%209872>*

On Sun, Jul 10, 2016 at 4:54 PM, Kant Kodali  wrote:

> Hi Guys,
>
> I installed a 3 node Cassandra cluster on AWS and my replication factor is
> 3. I am trying to insert some data into a table. I set the consistency
> level of QUORUM at a Cassandra Session level. It only inserts into one node
> and unable to talk to other nodes because it is trying to contact other
> nodes through private IP and obviously that is failing so I am not sure how
> to change settings in say cassandra.yaml or somewhere such that rpc_address
> in system.peers table is updated to public IP's? I tried changing the seeds
> to all public IP's that didn't work as it looks like ec2 instances cannot
> talk to each other using public IP's. any help would be appreciated!
>
> Thanks,
> kant
>