Re: Cassandra 3.10 - Hints & Dropped messages logs Vs Cass 2.x version

[Anumod Mullachery]

Okay ..

Thanks,will check ..

Anumod
PA,USA

Sent from my iPhone

> On Nov 2, 2017, at 5:40 PM, kurt greaves  wrote:
> 
> Well, pretty sure they still are. at least the mutation one is. but you 
> should really use the dedicated metrics for this.
> 
>> On 3 Nov. 2017 01:38, "Anumod Mullachery"  
>> wrote:
>> thanks ..
>> 
>> so the dropped hints & messages are not captured in cassandra logs, post 3.x 
>> vs 2.x.
>> 
>> -Anumod
>> 
>> 
>> 
>>> On Wed, Nov 1, 2017 at 4:50 PM, kurt greaves  wrote:
>>> You can get dropped message statistics over JMX. for example nodetool 
>>> tpstats has a counter for dropped hints from startup. that would be the 
>>> preferred method for tracking this info, rather than parsing logs
>>> 
>>> On 2 Nov. 2017 6:24 am, "Anumod Mullachery"  
>>> wrote:
>>> 
>>> Hi All,
>>> 
>>> In cassandra  v 2.1.15 , I'm able to pull the hints drop and dropped 
>>> messages from cassandra.log as below-
>>> 
>>> 
>>> dropped hints-->
>>> 
>>> "/opt/xcal/apps/cassandra/logs/cassandra.log--> 
>>> HintedHandoffMetrics.java:79 - /96.115.91.69 has 5 dropped hints, because 
>>> node is down past configured hint window."
>>> 
>>> Dropped messages -->
>>> 
>>> "/opt/xcal/apps/cassandra/logs/cassandra.log--> NFO 
>>> MessagingService 1 MUTATION messages dropped in last 5000ms"
>>> 
>>> 
>>> But in Cassandra V 3.10 , I'm not able to get the cassandra logs as v 
>>> 2.1.15.
>>> 
>>> I'm not able to get any info from the cassandra logs for dropped hints & 
>>> dropped messages. ( I was testing this on Test cluster by stopping the 
>>> cassandra services on one of the node , where the hints window is set to 05 
>>> Mins and kept the node down for 1 hour , and monitoring the cassandra logs, 
>>> but nothing generated on dropped hints on any other nodes in the cluster ).
>>> 
>>> The only message I found is on the down node is that - "Paused hints 
>>> dispatch".
>>> 
>>> Can some one put some light on this issue on 3.10 , is there any changes in 
>>> the hints & dropped messages , logs or the process.
>>> 
>>> thanks in advance,
>>> 
>>> regards,
>>> 
>>> Anumod.
>>> 
>>> 
>> 

Re: Cassandra 3.10 - Hints & Dropped messages logs Vs Cass 2.x version

[kurt greaves]

Well, pretty sure they still are. at least the mutation one is. but you
should really use the dedicated metrics for this.

On 3 Nov. 2017 01:38, "Anumod Mullachery" 
wrote:

> thanks ..
>
> so the dropped hints & messages are not captured in cassandra logs, post
> 3.x vs 2.x.
>
> -Anumod
>
>
>
> On Wed, Nov 1, 2017 at 4:50 PM, kurt greaves  wrote:
>
>> You can get dropped message statistics over JMX. for example nodetool
>> tpstats has a counter for dropped hints from startup. that would be the
>> preferred method for tracking this info, rather than parsing logs
>>
>> On 2 Nov. 2017 6:24 am, "Anumod Mullachery" 
>> wrote:
>>
>>
>> Hi All,
>>
>> In cassandra  v 2.1.15 , I'm able to pull the hints drop and dropped
>> messages from cassandra.log as below-
>>
>>
>> dropped hints-->
>>
>> "/opt/xcal/apps/cassandra/logs/cassandra.log
>> 
>> --> HintedHandoffMetrics.java:79 - /96.115.91.69 has 5 dropped hints,
>> because node is down past configured hint window."
>>
>> Dropped messages -->
>>
>> "/opt/xcal/apps/cassandra/logs/cassandra.log
>> 
>> --> NFO MessagingService 1 MUTATION messages dropped in last 5000ms"
>>
>>
>> But in Cassandra *V 3.10* , I'm not able to get the cassandra logs as v
>> 2.1.15.
>>
>> I'm not able to get any info from the cassandra logs for dropped hints &
>> dropped messages. ( I was testing this on Test cluster by stopping the
>> cassandra services on one of the node , where the hints window is set to 05
>> Mins and kept the node down for 1 hour , and monitoring the cassandra logs,
>> but nothing generated on dropped hints on any other nodes in the cluster ).
>>
>> The only message I found is on the down node is that - "Paused hints
>> dispatch".
>>
>> Can some one put some light on this issue on 3.10 , is there any changes
>> in the hints & dropped messages , logs or the process.
>>
>> thanks in advance,
>>
>> regards,
>>
>> Anumod.
>>
>>
>>
>

Re: Cassandra 3.10 - Hints & Dropped messages logs Vs Cass 2.x version

[Anumod Mullachery]

thanks ..

so the dropped hints & messages are not captured in cassandra logs, post
3.x vs 2.x.

-Anumod



On Wed, Nov 1, 2017 at 4:50 PM, kurt greaves  wrote:

> You can get dropped message statistics over JMX. for example nodetool
> tpstats has a counter for dropped hints from startup. that would be the
> preferred method for tracking this info, rather than parsing logs
>
> On 2 Nov. 2017 6:24 am, "Anumod Mullachery" 
> wrote:
>
>
> Hi All,
>
> In cassandra  v 2.1.15 , I'm able to pull the hints drop and dropped
> messages from cassandra.log as below-
>
>
> dropped hints-->
>
> "/opt/xcal/apps/cassandra/logs/cassandra.log
> 
> --> HintedHandoffMetrics.java:79 - /96.115.91.69 has 5 dropped hints,
> because node is down past configured hint window."
>
> Dropped messages -->
>
> "/opt/xcal/apps/cassandra/logs/cassandra.log
> 
> --> NFO MessagingService 1 MUTATION messages dropped in last 5000ms"
>
>
> But in Cassandra *V 3.10* , I'm not able to get the cassandra logs as v
> 2.1.15.
>
> I'm not able to get any info from the cassandra logs for dropped hints &
> dropped messages. ( I was testing this on Test cluster by stopping the
> cassandra services on one of the node , where the hints window is set to 05
> Mins and kept the node down for 1 hour , and monitoring the cassandra logs,
> but nothing generated on dropped hints on any other nodes in the cluster ).
>
> The only message I found is on the down node is that - "Paused hints
> dispatch".
>
> Can some one put some light on this issue on 3.10 , is there any changes
> in the hints & dropped messages , logs or the process.
>
> thanks in advance,
>
> regards,
>
> Anumod.
>
>
>

Re: Cassandra 3.10 - Hints & Dropped messages logs Vs Cass 2.x version

[kurt greaves]

You can get dropped message statistics over JMX. for example nodetool
tpstats has a counter for dropped hints from startup. that would be the
preferred method for tracking this info, rather than parsing logs

On 2 Nov. 2017 6:24 am, "Anumod Mullachery" 
wrote:


Hi All,

In cassandra  v 2.1.15 , I'm able to pull the hints drop and dropped
messages from cassandra.log as below-


dropped hints-->

"/opt/xcal/apps/cassandra/logs/cassandra.log

--> HintedHandoffMetrics.java:79 - /96.115.91.69 has 5 dropped hints,
because node is down past configured hint window."

Dropped messages -->

"/opt/xcal/apps/cassandra/logs/cassandra.log

--> NFO MessagingService 1 MUTATION messages dropped in last 5000ms"


But in Cassandra *V 3.10* , I'm not able to get the cassandra logs as v
2.1.15.

I'm not able to get any info from the cassandra logs for dropped hints &
dropped messages. ( I was testing this on Test cluster by stopping the
cassandra services on one of the node , where the hints window is set to 05
Mins and kept the node down for 1 hour , and monitoring the cassandra logs,
but nothing generated on dropped hints on any other nodes in the cluster ).

The only message I found is on the down node is that - "Paused hints
dispatch".

Can some one put some light on this issue on 3.10 , is there any changes in
the hints & dropped messages , logs or the process.

thanks in advance,

regards,

Anumod.

Re: Cassandra 3.10 Bootstrap- Error

[Anumod Mullachery]

Hi All,

thanks for all your inputs, appreciate it.

the issue resolved , nodes are able to join.

Pls find the solution I applied,


: Enable 256 bit encryption

  a : Copy the jce_policy-8.zip from  ..  to all nodes.

  b : Unzip jce_policy-8.zip,

  c : Copy local_policy.jar  and US_export_policy.jar from
UnlimitedJCEPolicyJDK8/ to /usr/java/jdk1.8.0_102/jre/lib/security/.

(or the latest java version directory being used )

& make sure the cassandra-topology.properties file details ; are in sync
with joining nodes.

restart the nodes.


regards

Anumod.



On Tue, Oct 24, 2017 at 9:12 AM, Dipan Shah  wrote:

> Hi Anumod,
>
>
> I faced the same issue with 3.11 and I'll suggest you first go through
> this link to check if the new node is able to communicate back on forth on
> the required port with the seed node.
>
>
> https://support.datastax.com/hc/en-us/articles/209691483-
> Bootstap-fails-with-Unable-to-gossip-with-any-seeds-yet-new-
> node-can-connect-to-seed-nodes
>
> 
> Bootstap fails with "Unable to gossip with any seeds" yet ...
> 
> support.datastax.com
> DataStax Support; DataStax Enterprise; Install/Upgrade; Bootstap fails
> with "Unable to gossip with any seeds" yet new node can connect to seed
> nodes
>
> This will mostly be the issue but even if that is not solving your
> problem, check the following points:
>
>
> 1) Check free disk space on the seed nodes. There should be sufficient
> free space for data migration to the new node.
>
> 2) Check logs of the seed nodes and see if there are any errors. I found
> some gossip file corruption on one of the seed nodes.
>
> 3) Finally, restart server\cassandra services on the seed nodes and see if
> that helps.
>
>
> Do let me know if this solved your problem.
>
>
>
> Thanks,
>
> Dipan Shah
>
>
> --
> *From:* Anumod Mullachery 
> *Sent:* Tuesday, October 24, 2017 2:12 AM
> *To:* user@cassandra.apache.org
> *Subject:* Cassandra 3.10 Bootstrap- Error
>
> Hi,
>
> We are using cassandra *3.10* , with *Network topology strategy* , &* 2
> DC* having *only 1 node each*.
>
> We are trying to add New nodes (auto_bootstrap: true) in yaml ,  but
> getting the below error-
>
> In the Seed nodes list, we have provided both the existing nodes from both
> DC(total -2 nodes). & tried with different option, by keeping only 1 node,
> but no hope.
>
>
> 2017-10-23 20:06:31,739 [MessagingService-Outgoing-/96.115.209.92-Gossip]
> WARN   SSLFactory.java:221 - Filtering out [TLS_RSA_WITH_AES_256_CBC_SHA]
> as it isn't supported by the socket
> 2017-10-23 20:06:31,739 [MessagingService-Outgoing-/96.115.209.92-Gossip]
> ERROR  OutboundTcpConnection.java:487 - SSL handshake error for outbound
> connection to 15454e08[SSL_NULL_WITH_NULL_NULL: Socket[addr=/96.115.209.92
> ,port=10145,localport=60859]]
> javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is
> disabled or cipher suites are inappropriate)
>
>
> *2017-10-23 20:06:32,655 [main] ERROR  CassandraDaemon.java:752 -
> Exception encountered during startup java.lang.RuntimeException: Unable to
> gossip with any seeds*
>
> 2017-10-23 20:06:32,666 [StorageServiceShutdownHook] INFO
> HintsService.java:221 - Paused hints dispatch
> 2017-10-23 20:06:32,667 [StorageServiceShutdownHook] WARN
> Gossiper.java:1514 - No local state, state is in silent shutdown, or node
> hasn't joined, not announcing shutdown
> 2017-10-23 20:06:32,667 [StorageServiceShutdownHook] INFO
> MessagingService.java:964 - Waiting for messaging service to quiesce
> 2017-10-23 20:06:32,667 [ACCEPT-/96.115.208.150] INFO
> MessagingService.java:1314 - MessagingService has terminated the accept()
> thread
> 2017-10-23 20:06:33,134 [StorageServiceShutdownHook] INFO
> HintsService.java:221 - Paused hints dispatch
>
> Can some one able to put some light on this issue, will be a great help.
>
> thanks in advance,
>
> - regards
>
> Anumod.
>

Re: Cassandra 3.10 Bootstrap- Error

[Dipan Shah]

Hi Anumod,


I faced the same issue with 3.11 and I'll suggest you first go through this 
link to check if the new node is able to communicate back on forth on the 
required port with the seed node.


https://support.datastax.com/hc/en-us/articles/209691483-Bootstap-fails-with-Unable-to-gossip-with-any-seeds-yet-new-node-can-connect-to-seed-nodes

[http://p8.zdassets.com/hc/settings_assets/31686/200039586/dvv6wj1TrSrpmATlV5ibLw-DataStax-whitelogo.png]

Bootstap fails with "Unable to gossip with any seeds" yet 
...
support.datastax.com
DataStax Support; DataStax Enterprise; Install/Upgrade; Bootstap fails with 
"Unable to gossip with any seeds" yet new node can connect to seed nodes


This will mostly be the issue but even if that is not solving your problem, 
check the following points:


1) Check free disk space on the seed nodes. There should be sufficient free 
space for data migration to the new node.

2) Check logs of the seed nodes and see if there are any errors. I found some 
gossip file corruption on one of the seed nodes.

3) Finally, restart server\cassandra services on the seed nodes and see if that 
helps.


Do let me know if this solved your problem.



Thanks,

Dipan Shah



From: Anumod Mullachery 
Sent: Tuesday, October 24, 2017 2:12 AM
To: user@cassandra.apache.org
Subject: Cassandra 3.10 Bootstrap- Error

Hi,

We are using cassandra 3.10 , with Network topology strategy , & 2 DC having 
only 1 node each.

We are trying to add New nodes (auto_bootstrap: true) in yaml ,  but getting 
the below error-

In the Seed nodes list, we have provided both the existing nodes from both 
DC(total -2 nodes). & tried with different option, by keeping only 1 node, but 
no hope.


2017-10-23 20:06:31,739 [MessagingService-Outgoing-/96.115.209.92-Gossip] WARN  
 SSLFactory.java:221 - Filtering out [TLS_RSA_WITH_AES_256_CBC_SHA] as it isn't 
supported by the socket
2017-10-23 20:06:31,739 [MessagingService-Outgoing-/96.115.209.92-Gossip] ERROR 
 OutboundTcpConnection.java:487 - SSL handshake error for outbound connection 
to 15454e08[SSL_NULL_WITH_NULL_NULL: 
Socket[addr=/96.115.209.92,port=10145,localport=60859]]
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is 
disabled or cipher suites are inappropriate)

2017-10-23 20:06:32,655 [main] ERROR  CassandraDaemon.java:752 - Exception 
encountered during startup
java.lang.RuntimeException: Unable to gossip with any seeds

2017-10-23 20:06:32,666 [StorageServiceShutdownHook] INFO   
HintsService.java:221 - Paused hints dispatch
2017-10-23 20:06:32,667 [StorageServiceShutdownHook] WARN   Gossiper.java:1514 
- No local state, state is in silent shutdown, or node hasn't joined, not 
announcing shutdown
2017-10-23 20:06:32,667 [StorageServiceShutdownHook] INFO   
MessagingService.java:964 - Waiting for messaging service to quiesce
2017-10-23 20:06:32,667 [ACCEPT-/96.115.208.150] INFO   
MessagingService.java:1314 - MessagingService has terminated the accept() thread
2017-10-23 20:06:33,134 [StorageServiceShutdownHook] INFO   
HintsService.java:221 - Paused hints dispatch

Can some one able to put some light on this issue, will be a great help.

thanks in advance,

- regards

Anumod.

Re: Cassandra 3.10 Bootstrap- Error

[kurt greaves]

Looks like you're having SSL issues. Is the new node configured with the
same internode_encryption settings as the existing nodes?.

No appropriate protocol (protocol is disabled or cipher suites are
> inappropriate)

Implies the new node is making a connection without SSL or the wrong
ciphers.
​

Re: cassandra 3.10

[Michael Shuler]

On 05/12/2017 01:11 PM, Gopal, Dhruva wrote:
> Since, we’re trying to qualify this for Production, 3.11 isn’t
> officially released, yet is it – it’s why we’re planning on using
> 3.10. The concern stems from the build failing with byteman. We’re
> novices at building our own rpms for Cassandra and are concerned that
> there may be other issues with the 3.10 release and maybe we should
> hold off till 3.11 is released and ready. Any opinions/feedback will
> help.

Here's the current changelog from 3.10 -> 3.11.0
https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt#L1-L115

That's a lot of fixed bugs since 3.10, so use that information as you
see fit.

The 3.11.0 release is currently down to making test fixes and/or
tracking down the last few remaining bugs, if test failures are due to
actual bugs.

The 3.11.X release series will be a long-term maintenance branch, so
fixes will be ongoing in this branch and new releases of 3.11.X will be
made when needed.

If you are working on evaluating a release for production, I would
suggest that evaluating 3.11.0 now would be a better choice, and your
byteman issues are already fixed in-tree, so no hacking around and doing
your own thing. 3.10 won't ever get updated, so if you need fixes for
issues you might find there, the path would be to upgrade to 3.11.X
anyway, so it doesn't make sense to me to start on 3.10.

If you have additional RPM package fixes for the cassandra-3.11 branch
and want to get them in for the 3.11.0 release, please include those on:
https://issues.apache.org/jira/browse/CASSANDRA-13433

Want to build RPMS easily and directly from git branches? This is where
the project is working on that build infrastructure to streamline
releases, and can be used to build packages on your own. See the README on:
https://github.com/apache/cassandra-builds

-- 
Kind regards,
Michael Shuler

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

Re: cassandra 3.10

[Gopal, Dhruva]

Hi Anthony –
  The link you shared below is where we initially started. That build fails 
(there is an issue with byteman as indicated by this Jira: 
https://issues.apache.org/jira/browse/CASSANDRA-13316). The source tarball 
already exists (released version), so we decided to skip rebuilding the 
artifacts and just pulled the release tarball from: 
http://apache.mirrors.tds.net/cassandra/3.10/apache-cassandra-3.10-src.tar.gz 
and created an rpm build with that. We did use the orginal spec and made a few 
minor tweaks to it. Basically, the tweaks were:

-  Apply the patches when doing the build (one was for byteman, the 
other was a change to the Cassandra unit file to make it unkillable by 
oom-killer).

-  Post install/erase actions (systemctl commands – such as reloading 
the daemon, autostarting the service etc).

That’s pretty much it, everything else should be the same as the original spec. 
Attaching it for convenience. Since, we’re trying to qualify this for 
Production, 3.11 isn’t officially released, yet is it – it’s why we’re planning 
on using 3.10. The concern stems from the build failing with byteman. We’re 
novices at building our own rpms for Cassandra and are concerned that there may 
be other issues with the 3.10 release and maybe we should hold off till 3.11 is 
released and ready. Any opinions/feedback will help.

Regards,
Dhruva


From: Anthony Grasso <anthony.gra...@gmail.com>
Date: Thursday, May 11, 2017 at 5:06 PM
To: "Gopal, Dhruva" <dhruva.go...@aspect.com>
Cc: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: cassandra 3.10

Hi Dhruva,

There are definitely some performance improvements to Storage Engine in 
Cassandra 3.10 which make it worth the upgrade. Note that Cassandra 3.11 has 
further bug fixes and it may be worth considering a migration to that version.

Regarding the issue of building a Cassandra 3.10 RPM, it sounds like the team 
have built their own custom spec file? Has the team looked at using the project 
spec file and associated instructions in Apache Cassandra GitHub mirror?

https://github.com/apache/cassandra/tree/cassandra-3.10/redhat

Kind regards,
Anthony


On 11 May 2017 at 14:20, Gopal, Dhruva 
<dhruva.go...@aspect.com<mailto:dhruva.go...@aspect.com>> wrote:
Hi –
  We’re currently on 3.9 and have been told that Cassandra 3.10 is a more 
stable version to be on. We’ve been using the datastax-ddc rpms in our 
production and dev environments (on 3.9) and it appears there is no 3.10 rpm 
version out yet. We tried to build our own rpm (our devops processes use rpms, 
so changing to using tarballs is not easily done) and found that the build 
process fails (to do with the byteman-3.0.3 jar) that we manage to patch and 
get working (with rpmbuild). My concerns/questions are these:

-  Is the 3.10 version actually stable enough given that the build 
failed (we obtained the source from this location: 
http://apache.mirrors.tds.net/cassandra/3.10/apache-cassandra-3.10-src.tar.gz) 
and used the attached patch file for byteman during the build process)?

-  Are there any other issues with the binaries that we need to be 
aware of (other patches)?

I’m concerned that there may be other issues and that we really won’t know 
since we’re not Cassandra experts, so looking for feedback from this group on 
whether we should just stay with 3.9 or if it’s safe to proceed with this 
approach. I can share the spec file and patch files that we’ve setup for the 
build process, if desired.


Regards,
DHRUVA GOPAL
sr. MANAGER, ENGINEERING
REPORTING, ANALYTICS AND BIG DATA
+1 408.325.2011<tel:+1%20408-325-2011> WORK
+1 408.219.1094<tel:+1%20408-219-1094> MOBILE
UNITED STATES
dhruva.go...@aspect.com<mailto:dhruva.go...@aspect.com>
aspect.com<http://www.aspect.com/>
[scription: http://webapp2.aspect.com/EmailSigLogo-rev.jpg]

This email (including any attachments) is proprietary to Aspect Software, Inc. 
and may contain information that is confidential. If you have received this 
message in error, please do not read, copy or forward this message. Please 
notify the sender immediately, delete it from your system and destroy any 
copies. You may not further disclose or distribute this email or its 
attachments.


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

This email (including any attachments) is proprietary to Aspect Software, Inc. 
and may contain information that is confidential. If you have received this 
message in error, please do not read, copy or forward this message. Please 
notify the sender immediately, delete it from your system and destroy any 
copies. You may not further disclose or distribute th

Re: cassandra 3.10

[Anthony Grasso]

Hi Dhruva,

There are definitely some performance improvements to Storage Engine in
Cassandra 3.10 which make it worth the upgrade. Note that Cassandra 3.11
has further bug fixes and it may be worth considering a migration to that
version.

Regarding the issue of building a Cassandra 3.10 RPM, it sounds like the
team have built their own custom spec file? Has the team looked at using
the project spec file and associated instructions in Apache Cassandra
GitHub mirror?

https://github.com/apache/cassandra/tree/cassandra-3.10/redhat

Kind regards,
Anthony


On 11 May 2017 at 14:20, Gopal, Dhruva  wrote:

> Hi –
>
>   We’re currently on 3.9 and have been told that Cassandra 3.10 is a more
> stable version to be on. We’ve been using the datastax-ddc rpms in our
> production and dev environments (on 3.9) and it appears there is no 3.10
> rpm version out yet. We tried to build our own rpm (our devops processes
> use rpms, so changing to using tarballs is not easily done) and found that
> the build process fails (to do with the byteman-3.0.3 jar) that we manage
> to patch and get working (with rpmbuild). My concerns/questions are these:
>
> -  Is the 3.10 version actually stable enough given that the
> build failed (we obtained the source from this location:
> http://apache.mirrors.tds.net/cassandra/3.10/apache-
> cassandra-3.10-src.tar.gz) and used the attached patch file for byteman
> during the build process)?
>
> -  Are there any other issues with the binaries that we need to
> be aware of (other patches)?
>
>
>
> I’m concerned that there may be other issues and that we really won’t know
> since we’re not Cassandra experts, so looking for feedback from this group
> on whether we should just stay with 3.9 or if it’s safe to proceed with
> this approach. I can share the spec file and patch files that we’ve setup
> for the build process, if desired.
>
>
>
>
>
> Regards,
>
> *DHRUVA GOPAL*
>
> *sr. MANAGER, ENGINEERING*
>
> *REPORTING, ANALYTICS AND BIG DATA*
>
> *+1 408.325.2011 <+1%20408-325-2011>* *WORK*
>
> *+1 408.219.1094 <+1%20408-219-1094>* *MOBILE*
>
> *UNITED STATES*
>
> *dhruva.go...@aspect.com  *
>
> *aspect.com *
>
> [image: escription: http://webapp2.aspect.com/EmailSigLogo-rev.jpg]
>
>
> This email (including any attachments) is proprietary to Aspect Software,
> Inc. and may contain information that is confidential. If you have received
> this message in error, please do not read, copy or forward this message.
> Please notify the sender immediately, delete it from your system and
> destroy any copies. You may not further disclose or distribute this email
> or its attachments.
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Kant Kodali]

Thanks a lot guys!

On Tue, May 9, 2017 at 7:32 AM, Alexander Dejanovski  wrote:

> Hi Kant,
>
> Unless you provide the full partition key, I see no way for Cassandra to
> avoid doing a full table scan.
> In order to know on which specific nodes to search (and in which sstables
> ,etc...) it needs to have a token. The token is a hash of the whole
> partition key.
> For a specific value of column "a" and different values of column "b" you
> always end up with different tokens that have no guaranty to be stored on
> the same node.
> After that, bloom filters, partition indexes, etc... require the full
> token too, so a full scan is further necessary on each node to get the
> data.
>
> TL;DR : no way to avoid a full cluster scan unless you provide the full
> partition key in your where clause.
>
> Cheers,
>
> On Tue, May 9, 2017 at 4:24 PM Jon Haddad 
> wrote:
>
>> Nope, I didn’t comment on that query.   I specifically answered your
>> question about "select * from hello where a='foo' allow filtering;”
>>
>> The query you’ve listed here looks like it would also do a full table
>> scan (again, I don’t see how it would be avoided).
>>
>> I recommend firing up a 3 node cluster using CCM, creating a key space
>> with RF=1, and seeing what it does.
>>
>> On May 9, 2017, at 9:12 AM, Kant Kodali  wrote:
>>
>> Hi,
>>
>> Are you saying The following query select max(b) from hello where a='a1'
>> allow filtering; doesn't result in a table scan? I got the result for
>> this query and yes I just tried tracing it and looks like it is indeed
>> doing a table scan on ReadStage-2 although I am not sure if I am
>> interpreting it right? Finally is there anyway to prevent table scan while
>> providing the partial partition key and get the max b ?
>>
>> 
>> ​
>>
>>
>> On Tue, May 9, 2017 at 6:33 AM, Jon Haddad 
>> wrote:
>>
>>> I don’t see any way it wouldn’t.  Have you tried tracing it?
>>>
>>> > On May 9, 2017, at 8:32 AM, Kant Kodali  wrote:
>>> >
>>> > Hi All,
>>> >
>>> > It looks like Cassandra 3.10 has partial partition key search but does
>>> it result in a table scan? for example I can have the following
>>> >
>>> > create table hello(
>>> > a text,
>>> > b int,
>>> > c text,
>>> > d text,
>>> > primary key((a,b), c)
>>> > );
>>> >
>>> > Now I can do select * from hello where a='foo' allow filtering;// This
>>> works in 3.10 but I wonder if this query results in table scan and if so is
>>> there any way to limit such that I get max b?
>>> >
>>> > Thanks!
>>>
>>>
>> --
> -
> Alexander Dejanovski
> France
> @alexanderdeja
>
> Consultant
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Alexander Dejanovski]

Hi Kant,

Unless you provide the full partition key, I see no way for Cassandra to
avoid doing a full table scan.
In order to know on which specific nodes to search (and in which sstables
,etc...) it needs to have a token. The token is a hash of the whole
partition key.
For a specific value of column "a" and different values of column "b" you
always end up with different tokens that have no guaranty to be stored on
the same node.
After that, bloom filters, partition indexes, etc... require the full token
too, so a full scan is further necessary on each node to get the data.

TL;DR : no way to avoid a full cluster scan unless you provide the full
partition key in your where clause.

Cheers,

On Tue, May 9, 2017 at 4:24 PM Jon Haddad  wrote:

> Nope, I didn’t comment on that query.   I specifically answered your
> question about "select * from hello where a='foo' allow filtering;”
>
> The query you’ve listed here looks like it would also do a full table scan
> (again, I don’t see how it would be avoided).
>
> I recommend firing up a 3 node cluster using CCM, creating a key space
> with RF=1, and seeing what it does.
>
> On May 9, 2017, at 9:12 AM, Kant Kodali  wrote:
>
> Hi,
>
> Are you saying The following query select max(b) from hello where a='a1'
> allow filtering; doesn't result in a table scan? I got the result for
> this query and yes I just tried tracing it and looks like it is indeed
> doing a table scan on ReadStage-2 although I am not sure if I am
> interpreting it right? Finally is there anyway to prevent table scan while
> providing the partial partition key and get the max b ?
>
> 
> ​
>
>
> On Tue, May 9, 2017 at 6:33 AM, Jon Haddad 
> wrote:
>
>> I don’t see any way it wouldn’t.  Have you tried tracing it?
>>
>> > On May 9, 2017, at 8:32 AM, Kant Kodali  wrote:
>> >
>> > Hi All,
>> >
>> > It looks like Cassandra 3.10 has partial partition key search but does
>> it result in a table scan? for example I can have the following
>> >
>> > create table hello(
>> > a text,
>> > b int,
>> > c text,
>> > d text,
>> > primary key((a,b), c)
>> > );
>> >
>> > Now I can do select * from hello where a='foo' allow filtering;// This
>> works in 3.10 but I wonder if this query results in table scan and if so is
>> there any way to limit such that I get max b?
>> >
>> > Thanks!
>>
>>
> --
-
Alexander Dejanovski
France
@alexanderdeja

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Jon Haddad]

Output from both queries, demonstrating full cluster scans:

https://gist.github.com/rustyrazorblade/c4947fc37da85bca50e08aa1ef3c7a06 


Jon

> On May 9, 2017, at 9:24 AM, Jon Haddad  wrote:
> 
> Nope, I didn’t comment on that query.   I specifically answered your question 
> about "select * from hello where a='foo' allow filtering;”
> 
> The query you’ve listed here looks like it would also do a full table scan 
> (again, I don’t see how it would be avoided).
> 
> I recommend firing up a 3 node cluster using CCM, creating a key space with 
> RF=1, and seeing what it does.  
> 
>> On May 9, 2017, at 9:12 AM, Kant Kodali > > wrote:
>> 
>> Hi,
>> 
>> Are you saying The following query select max(b) from hello where a='a1' 
>> allow filtering; doesn't result in a table scan? I got the result for this 
>> query and yes I just tried tracing it and looks like it is indeed doing a 
>> table scan on ReadStage-2 although I am not sure if I am interpreting it 
>> right? Finally is there anyway to prevent table scan while providing the 
>> partial partition key and get the max b ?
>> 
>> 
>> ​
>> 
>> 
>> On Tue, May 9, 2017 at 6:33 AM, Jon Haddad > > wrote:
>> I don’t see any way it wouldn’t.  Have you tried tracing it?
>> 
>> > On May 9, 2017, at 8:32 AM, Kant Kodali > > > wrote:
>> >
>> > Hi All,
>> >
>> > It looks like Cassandra 3.10 has partial partition key search but does it 
>> > result in a table scan? for example I can have the following
>> >
>> > create table hello(
>> > a text,
>> > b int,
>> > c text,
>> > d text,
>> > primary key((a,b), c)
>> > );
>> >
>> > Now I can do select * from hello where a='foo' allow filtering;// This 
>> > works in 3.10 but I wonder if this query results in table scan and if so 
>> > is there any way to limit such that I get max b?
>> >
>> > Thanks!
>> 
>> 
> 

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Jon Haddad]

Nope, I didn’t comment on that query.   I specifically answered your question 
about "select * from hello where a='foo' allow filtering;”

The query you’ve listed here looks like it would also do a full table scan 
(again, I don’t see how it would be avoided).

I recommend firing up a 3 node cluster using CCM, creating a key space with 
RF=1, and seeing what it does.  

> On May 9, 2017, at 9:12 AM, Kant Kodali  wrote:
> 
> Hi,
> 
> Are you saying The following query select max(b) from hello where a='a1' 
> allow filtering; doesn't result in a table scan? I got the result for this 
> query and yes I just tried tracing it and looks like it is indeed doing a 
> table scan on ReadStage-2 although I am not sure if I am interpreting it 
> right? Finally is there anyway to prevent table scan while providing the 
> partial partition key and get the max b ?
> 
> 
> ​
> 
> 
> On Tue, May 9, 2017 at 6:33 AM, Jon Haddad  > wrote:
> I don’t see any way it wouldn’t.  Have you tried tracing it?
> 
> > On May 9, 2017, at 8:32 AM, Kant Kodali  > > wrote:
> >
> > Hi All,
> >
> > It looks like Cassandra 3.10 has partial partition key search but does it 
> > result in a table scan? for example I can have the following
> >
> > create table hello(
> > a text,
> > b int,
> > c text,
> > d text,
> > primary key((a,b), c)
> > );
> >
> > Now I can do select * from hello where a='foo' allow filtering;// This 
> > works in 3.10 but I wonder if this query results in table scan and if so is 
> > there any way to limit such that I get max b?
> >
> > Thanks!
> 
> 

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Daniel Hölbling-Inzko]

If you have to allow filtering for the query to work it usually always
results in a table scan.

greetings Daniel

On Tue, 9 May 2017 at 15:33 Jon Haddad  wrote:

> I don’t see any way it wouldn’t.  Have you tried tracing it?
>
> > On May 9, 2017, at 8:32 AM, Kant Kodali  wrote:
> >
> > Hi All,
> >
> > It looks like Cassandra 3.10 has partial partition key search but does
> it result in a table scan? for example I can have the following
> >
> > create table hello(
> > a text,
> > b int,
> > c text,
> > d text,
> > primary key((a,b), c)
> > );
> >
> > Now I can do select * from hello where a='foo' allow filtering;// This
> works in 3.10 but I wonder if this query results in table scan and if so is
> there any way to limit such that I get max b?
> >
> > Thanks!
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

Re: Cassandra 3.10 has partial partition key search but does it result in a table scan?

[Jon Haddad]

I don’t see any way it wouldn’t.  Have you tried tracing it?

> On May 9, 2017, at 8:32 AM, Kant Kodali  wrote:
> 
> Hi All,
> 
> It looks like Cassandra 3.10 has partial partition key search but does it 
> result in a table scan? for example I can have the following
> 
> create table hello(
> a text,
> b int,
> c text,
> d text,
> primary key((a,b), c)
> );
> 
> Now I can do select * from hello where a='foo' allow filtering;// This works 
> in 3.10 but I wonder if this query results in table scan and if so is there 
> any way to limit such that I get max b?
> 
> Thanks!


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

RE: Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Anton PASSIOUK]

Thank you Edward.

From: Edward Capriolo [mailto:edlinuxg...@gmail.com]
Sent: Friday, March 31, 2017 4:22 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

I created https://issues.apache.org/jira/browse/CASSANDRA-13396 for you

https://issues.apache.org/jira/browse/CASSANDRA-13396

/**


 * The purpose of this class is


 */

this purpose of this class is ...what ? this class is who? sicka sicka slim 
shady.


On Thu, Mar 30, 2017 at 1:48 PM, Anton PASSIOUK 
<anton.passi...@hsoftware.com<mailto:anton.passi...@hsoftware.com>> wrote:
Hello

After upgrading from Cassandra 3.6 to 3.10 I have suddenly started having 
errors like this:

java.lang.ClassCastException: org.slf4j.impl.JDK14LoggerAdapter cannot be cast 
to ch.qos.logback.classic.Logger
at 
org.apache.cassandra.cql3.functions.ThreadAwareSecurityManager.install(ThreadAwareSecurityManager.java:82)
at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:193)
at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601)
at 
com.ingalys.cassandra.CassandraWrapper.(CassandraWrapper.java:150)
at com.ingalys.cassandra.Builder.build(Builder.java:22)
at 
com.ingalys.soa.ServiceContainer$1.lambda$run$0(ServiceContainer.java:172)
at 
com.ingalys.fmk2.util.ThrowingFunction.apply(ThrowingFunction.java:14)
at 
com.ingalys.fmk2.util.PromiseImpl.lambda$thenCompose$5(PromiseImpl.java:166)

I am embedding Cassandra nodes in a container of mine and it happens that there 
are several slf4j bindings that are transitively brought to the classpath by 
other dependencies.
I have read that in this case slf4j chooses one of the bindings more-or-less 
randomly, in my case it takes the "jdk14" implementation and makes Cassandra 
daemon (and me too) unhappy because there is a hard-coded cast to 
ch.qos.logback.classic.Logger in ThreadAwareSecurityManager:

https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/ThreadAwareSecurityManager.java#L83

Of course this crashes if another slf4j binding is used (by accident like me, 
or as a conscious choice) so I was wondering if this code should check the type 
of the logger before cast and adopt some fallback behavior if slf4j is not 
bound to logback?

Thanks and regards,
--
Anton PASSIOUK
Horizon Software - Trade Your Way
http://www.hsoftware.com/

Re: Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Edward Capriolo]

I created https://issues.apache.org/jira/browse/CASSANDRA-13396 for you

https://issues.apache.org/jira/browse/CASSANDRA-13396

/**
* The purpose of this class is
*/ this purpose of this class is ...what ? this class is who? sicka sicka
slim shady.

On Thu, Mar 30, 2017 at 1:48 PM, Anton PASSIOUK <
anton.passi...@hsoftware.com> wrote:

> Hello
>
> After upgrading from Cassandra 3.6 to 3.10 I have suddenly started having
> errors like this:
>
> java.lang.ClassCastException: org.slf4j.impl.JDK14LoggerAdapter cannot be
> cast to ch.qos.logback.classic.Logger
> at org.apache.cassandra.cql3.functions.ThreadAwareSecurityManager.
> install(ThreadAwareSecurityManager.java:82)
> at org.apache.cassandra.service.CassandraDaemon.setup(
> CassandraDaemon.java:193)
> at org.apache.cassandra.service.CassandraDaemon.activate(
> CassandraDaemon.java:601)
> at com.ingalys.cassandra.CassandraWrapper.(
> CassandraWrapper.java:150)
> at com.ingalys.cassandra.Builder.build(Builder.java:22)
> at com.ingalys.soa.ServiceContainer$1.lambda$run$
> 0(ServiceContainer.java:172)
> at com.ingalys.fmk2.util.ThrowingFunction.apply(
> ThrowingFunction.java:14)
> at com.ingalys.fmk2.util.PromiseImpl.lambda$
> thenCompose$5(PromiseImpl.java:166)
>
> I am embedding Cassandra nodes in a container of mine and it happens that
> there are several slf4j bindings that are transitively brought to the
> classpath by other dependencies.
> I have read that in this case slf4j chooses one of the bindings
> more-or-less randomly, in my case it takes the "jdk14" implementation and
> makes Cassandra daemon (and me too) unhappy because there is a hard-coded
> cast to ch.qos.logback.classic.Logger in ThreadAwareSecurityManager:
>
> https://github.com/apache/cassandra/blob/trunk/src/java/
> org/apache/cassandra/cql3/functions/ThreadAwareSecurityManager.java#L83
>
> Of course this crashes if another slf4j binding is used (by accident like
> me, or as a conscious choice) so I was wondering if this code should check
> the type of the logger before cast and adopt some fallback behavior if
> slf4j is not bound to logback?
>
> Thanks and regards,
> --
> Anton PASSIOUK
> Horizon Software - Trade Your Way
> http://www.hsoftware.com/
>
>
>
>
>