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

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,

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

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

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

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

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

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

Re: Cassandra 3.10 Bootstrap- Error

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

Re: Cassandra 3.10 Bootstrap- Error

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.

Re: Cassandra 3.10 Bootstrap- Error

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

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

Re: cassandra 3.10

pal, 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

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

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

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

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

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

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

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: > >

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

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

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

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

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

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

RE: Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

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

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