date:20170704

Re: UDF for sorting

2017-07-04 Thread Justin Cameron

Yes, it does - you'll just have to build for the 2.1.17 branch. You also
will have to use their alternative query syntax:
https://github.com/Stratio/cassandra-lucene-index/blob/branch-3.0.10/doc/documentation.rst#alternative-syntaxes

On Tue, 4 Jul 2017 at 17:27 techpyaasa .  wrote:

> Hi Justin,
>
> Thanks for the reply.
> We are using c*-2.1.17 , does lucene plugin works with this version??
>
> On Tue, Jul 4, 2017 at 4:49 AM, Justin Cameron 
> wrote:
>
>> While you can't do this with Cassandra, you can get the functionality you
>> want with the cassandra-lucene-plugin (
>> https://github.com/Stratio/cassandra-lucene-index/blob/branch-3.0.10/doc/documentation.rst#searching
>> ).
>>
>> Keep in mind that as with any secondary index there are
>> performance-related limitations:
>> https://github.com/Stratio/cassandra-lucene-index/blob/branch-3.0.10/doc/documentation.rst#performance-tips
>>
>>
>> On Tue, 4 Jul 2017 at 07:17 DuyHai Doan  wrote:
>>
>>> Plain answer is no you can't
>>>
>>> The reason is that UDF only transform column values on each row but does
>>> not have the ability to modify rows ordering
>>>
>>> On Mon, Jul 3, 2017 at 10:14 PM, techpyaasa . 
>>> wrote:
>>>
 Hi all,

 I have a table like

 CREATE TABLE ks.cf ( pk1 bigint, cc1 bigint, disp_name text , stat_obj
 text, status int, PRIMARY KEY (pk1, cc1)) WITH CLUSTERING ORDER BY (cc1 
 ASC)

 CREATE INDEX idx1 on ks.cf(status);

 I want to have a queries like
 *select * from ks.cf  where pk1=123 and cc1=345;*

 and
 *select * from ks.cf  where pk1=123 and status=1;*
 In this case , I want rows to be sorted based on 'disp_name' (asc/desc)
 .

 Can I achieve the same using UDF or anything else ?? (Sorry If my
 understanding about UDF is wrong).

 Thanks in advance
 TechPyaasa

>>>
>>> --
>>
>>
>> *Justin Cameron*Senior Software Engineer
>>
>>
>> 
>>
>>
>> This email has been sent on behalf of Instaclustr Pty. Limited
>> (Australia) and Instaclustr Inc (USA).
>>
>> This email and any attachments may contain confidential and legally
>> privileged information.  If you are not the intended recipient, do not copy
>> or disclose its content, but please reply to this email immediately and
>> highlight the error to the sender and then immediately delete the message.
>>
>
> --

*Justin Cameron*Senior Software Engineer

This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
and Instaclustr Inc (USA).

This email and any attachments may contain confidential and legally
privileged information.  If you are not the intended recipient, do not copy
or disclose its content, but please reply to this email immediately and
highlight the error to the sender and then immediately delete the message.

Re: Adding a New Node With The Same IP of an Old Node

2017-07-04 Thread Nitan Kainth

Try rolling restart of cluster as solution for schema version mismatch.


Sent from my iPhone

> On Jul 4, 2017, at 8:31 AM, Shalom Sagges  wrote:
> 
> Hi Experts, 
> 
> My plan is to upgrade the C* nodes' OS from Centos6 to Centos7. 
> Since an upgrade wasn't recommended I needed to install new machines with 
> Centos7 and join them to the cluster. 
> I didn't want to decommission/bootstrap dozens of nodes, so I decided to do 
> the following:
> Create a new machine
> Copy all data, schema data and commit logs using rsync from the old node to 
> the new one
> Stop Cassandra on the old node, copy the delta and shut the node down
> Change the hostname and IP address of the new node to the hostname and IP of 
> the old node.
> Start Cassandra on the new node. 
> My thought was that the "new" node will join the cluster as the "old" node 
> since it has all of its data and metadata, however, after Cassandra started 
> up, it saw all its peers in DN state. The same goes for the other nodes, that 
> saw the new node is DN state. 
> 
> I didn't find any errors or warnings in the logs, but I did see that the 
> schema version on the new node was different from the others( I'm assuming 
> that's the issue here?) 
> 
> 
> Functioning node
> nodetool describecluster
> Cluster Information:
> Name: MyCluster
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 503bf151-c59c-35a0-8350-ca73e82098f5: [x.x.x.32, x.x.x.126, 
> x.x.x.35, x.x.x.1, x.x.x.28, x.x.x.15, x.x.x.252, x.x.x.253, x.x.x.31]
> 
> UNREACHABLE: [x.x.x.2]
> 
> 
> New node
> nodetool describecluster
> Cluster Information:
> Name: MyCluster
> Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> dab67163-65d4-3895-82e6-ffc07bf5c17a: [x.x.x.2]
> 
> UNREACHABLE: [x.x.x.31, x.x.x.1, x.x.x.28, x.x.x.252, 
> x.x.x.253, x.x.x.15, x.x.x.126, x.x.x.35, x.x.x.32]
> 
> 
> I'd really REALLY appreciate some guidance. Did I do something wrong? Is 
> there a way to fix this? 
> 
> 
> Thanks a lot!
> 
> Shalom Sagges
> DBA
>   
> We Create Meaningful Connections
> 
>  
> 
> This message may contain confidential and/or privileged information. 
> If you are not the addressee or authorized to receive this on behalf of the 
> addressee you must not use, copy, disclose or take action based on this 
> message or any information herein. 
> If you have received this message in error, please advise the sender 
> immediately by reply email and delete this message. Thank you.

Re: RE: Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Subroto Barua

check firewall rules to/from .152 to seed nodes (telnet  


On Tuesday, July 4, 2017, 6:38:16 AM PDT, Jonathan Baynes 
 wrote:

#yiv3228115995 #yiv3228115995 -- _filtered #yiv3228115995 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv3228115995 
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv3228115995 
#yiv3228115995 p.yiv3228115995MsoNormal, #yiv3228115995 
li.yiv3228115995MsoNormal, #yiv3228115995 div.yiv3228115995MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv3228115995 a:link, 
#yiv3228115995 span.yiv3228115995MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv3228115995 a:visited, #yiv3228115995 
span.yiv3228115995MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv3228115995 
span.yiv3228115995EmailStyle17 {color:windowtext;}#yiv3228115995 
span.yiv3228115995EmailStyle18 {color:#1F497D;}#yiv3228115995 
.yiv3228115995MsoChpDefault {font-size:10.0pt;} _filtered #yiv3228115995 
{margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv3228115995 
div.yiv3228115995WordSection1 {}#yiv3228115995 
Hi Bhargav
 
  
 
  
 
I had this recently when making changes to a cluster, and It was down to the 
Listen_address & broadcast_address. Check your cassandra.yaml and make sure 
that your listen_address/broadcast_address and "seeds" values match. Make sure 
the Data folder is empty as well.
 
  
 
I would go through your yaml, be diligent its there that is the problem.
 
  
 
Thanks
 
J
 
  
 
  
 
From: Mokkapati, Bhargav (Nokia - IN/Chennai) 
[mailto:bhargav.mokkap...@nokia.com]
Sent: 04 July 2017 14:00
To: user@cassandra.apache.org
Subject: Cassandra issue “Unable to gossip with any seeds”
 
  
 
Hi Team,
 
  
 
I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”
 
  
 

 
  
 
I am using Apache Cassandra 3.0.6 version.
 
  
 
I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155
 
  
 
Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155
 
  
 
All the nodes have same Cassandra.yaml configuration file
 
  
 
I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.
 
  
 

 
  
 
  
 
Also node2 is pinging from seed nodes and vice versa.
 
  
 

 
  
 
  
 
Please let me know if any of you have faced the same issue and found the 
solution.
 
  
 
Thank you very much
 
  
 
Regards,
 
Bhargav
 
  
 
  
 
  
 
  
 
  
 
  
 


This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy it. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly 
forbidden. Tradeweb reserves the right to monitor all e-mail communications 
through its networks. If you do not wish to receive marketing emails about our 
products / services, please let us know by contacting us, either by email at 
contac...@tradeweb.com or by writing to us at the registered office of Tradeweb 
in the UK, which is: Tradeweb Europe Limited (company number 3912826), 1 Fore 
Street Avenue London EC2Y 9DT. To see our privacy policy, visit our website @ 
www.tradeweb.com.

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: jbod disk usage unequal

2017-07-04 Thread Micha

thanks for answering,

On 03.07.2017 20:01, Jeff Jirsa wrote:
> 
> 
> Is there a reason you feel it's required, other than being bothered by the 
> fact that they're not equal? 

Just out of interest. I'm not sure if it would spread the io better
between the disks if the files are spread more evenly on both disks .

>> Otherwise is a raid-0 setup the only option for a balanced disk usage?
> 
>  it doesn't REALLY matter how full it is, right?

Don't know, that's the question.
I think there may be io hotspots if mostly one disk is used until it's full.

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Adding a New Node With The Same IP of an Old Node

2017-07-04 Thread Shalom Sagges

Hi Experts,

My plan is to upgrade the C* nodes' OS from Centos6 to Centos7.
Since an upgrade wasn't recommended I needed to install new machines with
Centos7 and join them to the cluster.
I didn't want to decommission/bootstrap dozens of nodes, so I decided to do
the following:

   - Create a new machine
   - Copy all data, schema data and commit logs using rsync from the old
   node to the new one
   - Stop Cassandra on the old node, copy the delta and shut the node down
   - Change the hostname and IP address of the new node to the hostname and
   IP of the old node.
   - Start Cassandra on the new node.

My thought was that the "new" node will join the cluster as the "old" node
since it has all of its data and metadata, however, after Cassandra started
up, it saw all its peers in DN state. The same goes for the other nodes,
that saw the new node is DN state.

I didn't find any errors or warnings in the logs, but I did see that
the *schema
version* on the new node was different from the others( I'm assuming that's
the issue here?)


*Functioning node*
nodetool describecluster
Cluster Information:
Name: MyCluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
503bf151-c59c-35a0-8350-ca73e82098f5: [x.x.x.32, x.x.x.126,
x.x.x.35, x.x.x.1, x.x.x.28, x.x.x.15, x.x.x.252, x.x.x.253, x.x.x.31]

UNREACHABLE: [x.x.x.2]


*New node*
nodetool describecluster
Cluster Information:
Name: MyCluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
dab67163-65d4-3895-82e6-ffc07bf5c17a: [x.x.x.2]

UNREACHABLE: [x.x.x.31, x.x.x.1, x.x.x.28, x.x.x.252,
x.x.x.253, x.x.x.15, x.x.x.126, x.x.x.35, x.x.x.32]


I'd really REALLY appreciate some guidance. Did I do something wrong? Is
there a way to fix this?


Thanks a lot!

Shalom Sagges
DBA
 
 We Create Meaningful Connections

-- 
This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this 
message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

Merkle trees requests hanging

2017-07-04 Thread Jean Carlo

Hello.

What if a node send a merkle tree to its replica but this one would never
received by any network issues. The repair will be hanging eternally ? or
Should I modify  the parameter
# streaming_socket_timeout_in_ms: 0 to avoid this ?

Saludos

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

RE: Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Jonathan Baynes

Hi Bhargav


I had this recently when making changes to a cluster, and It was down to the 
Listen_address & broadcast_address. Check your cassandra.yaml and make sure 
that your listen_address/broadcast_address and "seeds" values match. Make sure 
the Data folder is empty as well.

I would go through your yaml, be diligent its there that is the problem.

Thanks
J


From: Mokkapati, Bhargav (Nokia - IN/Chennai) 
[mailto:bhargav.mokkap...@nokia.com]
Sent: 04 July 2017 14:00
To: user@cassandra.apache.org
Subject: Cassandra issue “Unable to gossip with any seeds”

Hi Team,

I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”

[cid:image001.jpg@01D2F4D3.1E74E5E0]

I am using Apache Cassandra 3.0.6 version.

I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155

Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155

All the nodes have same Cassandra.yaml configuration file

I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.

[cid:image002.png@01D2F4D3.1E74E5E0]


Also node2 is pinging from seed nodes and vice versa.

[cid:image003.png@01D2F4D3.1E74E5E0]


Please let me know if any of you have faced the same issue and found the 
solution.

Thank you very much

Regards,
Bhargav









This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy it. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly 
forbidden. Tradeweb reserves the right to monitor all e-mail communications 
through its networks. If you do not wish to receive marketing emails about our 
products / services, please let us know by contacting us, either by email at 
contac...@tradeweb.com or by writing to us at the registered office of Tradeweb 
in the UK, which is: Tradeweb Europe Limited (company number 3912826), 1 Fore 
Street Avenue London EC2Y 9DT. To see our privacy policy, visit our website @ 
www.tradeweb.com.

Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Mokkapati, Bhargav (Nokia - IN/Chennai)

Hi Team,

I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”

[cid:image003.jpg@01D2F4F3.8B790480]

I am using Apache Cassandra 3.0.6 version.

I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155

Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155

All the nodes have same Cassandra.yaml configuration file

I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.

[cid:image004.png@01D2F4F1.9773CC90]


Also node2 is pinging from seed nodes and vice versa.

[cid:image005.png@01D2F4F2.4B7CAA90]


Please let me know if any of you have faced the same issue and found the 
solution.

Thank you very much

Regards,
Bhargav

Sending merkle trees

2017-07-04 Thread Jean Carlo

Hello

In cassandra 2.1. When a replica has sent its merkle tree, Does it via
streaming ? which protocol does it use ?


Best regards

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

Re: UDF for sorting

2017-07-04 Thread techpyaasa .

Hi Justin,

Thanks for the reply.
We are using c*-2.1.17 , does lucene plugin works with this version??

On Tue, Jul 4, 2017 at 4:49 AM, Justin Cameron 
wrote:

> While you can't do this with Cassandra, you can get the functionality you
> want with the cassandra-lucene-plugin (https://github.com/Stratio/
> cassandra-lucene-index/blob/branch-3.0.10/doc/documentation.rst#searching
> ).
>
> Keep in mind that as with any secondary index there are
> performance-related limitations: https://github.
> com/Stratio/cassandra-lucene-index/blob/branch-3.0.10/doc/
> documentation.rst#performance-tips
>
> On Tue, 4 Jul 2017 at 07:17 DuyHai Doan  wrote:
>
>> Plain answer is no you can't
>>
>> The reason is that UDF only transform column values on each row but does
>> not have the ability to modify rows ordering
>>
>> On Mon, Jul 3, 2017 at 10:14 PM, techpyaasa . 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have a table like
>>>
>>> CREATE TABLE ks.cf ( pk1 bigint, cc1 bigint, disp_name text , stat_obj
>>> text, status int, PRIMARY KEY (pk1, cc1)) WITH CLUSTERING ORDER BY (cc1 ASC)
>>>
>>> CREATE INDEX idx1 on ks.cf(status);
>>>
>>> I want to have a queries like
>>> *select * from ks.cf  where pk1=123 and cc1=345;*
>>>
>>> and
>>> *select * from ks.cf  where pk1=123 and status=1;*
>>> In this case , I want rows to be sorted based on 'disp_name' (asc/desc) .
>>>
>>> Can I achieve the same using UDF or anything else ?? (Sorry If my
>>> understanding about UDF is wrong).
>>>
>>> Thanks in advance
>>> TechPyaasa
>>>
>>
>> --
>
>
> *Justin Cameron*Senior Software Engineer
>
>
> 
>
>
> This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
> and Instaclustr Inc (USA).
>
> This email and any attachments may contain confidential and legally
> privileged information.  If you are not the intended recipient, do not copy
> or disclose its content, but please reply to this email immediately and
> highlight the error to the sender and then immediately delete the message.
>

Re: UDF for sorting

Re: Adding a New Node With The Same IP of an Old Node

Re: RE: Cassandra issue “Unable to gossip with any seeds”

Re: jbod disk usage unequal

Adding a New Node With The Same IP of an Old Node

Merkle trees requests hanging

RE: Cassandra issue “Unable to gossip with any seeds”

Cassandra issue “Unable to gossip with any seeds”

Sending merkle trees

Re: UDF for sorting

10 matches

Site Navigation

Mail list logo

Footer information