Hi Anuja,
What your are looking for is provided as part of DSE :
https://docs.datastax.com/en/datastax_enterprise/5.0/datastax_enterprise/sec/auditEnabling.html
On 1 April 2017 at 20:15, Vladimir Yudovin wrote:
> Hi anuja,
>
> I don't thinks there is a way to do this without creating custom Cas
Further info - tablehistograms reports zeros for all percentiles for Read
Latency; tablestats also reports really low numbers for Bloom filter usage
(3-4 KiB, depending on node, whereas I'd expect orders of magnitude more
given other - less accessed - tables in this keyspace). This is the most
wri
Hi,
could you share your GC settings ? G1 or CMS ? Heap size, etc...
Thanks,
On Sun, Apr 2, 2017 at 10:30 PM Gopal, Dhruva
wrote:
> Hi –
>
> We’ve had what looks like an OOM situation with Cassandra (we have a
> dump file that got generated) in our staging (performance/load testing
> environ
Sounds like you want full auditing of CQL in the cluster. I have not seen
anything built into the open source version for that (but I could be missing
something). DataStax Enterprise does have an auditing feature.
Sean Durity
From: anuja jain [mailto:anujaja...@gmail.com]
Sent: Wednesday, Marc
Continuing to grasp at straws...
Is it possible that indexing is modifying the read path such that the
tablestats/tablehistograms output is no longer trustworthy? I notice more
realistic "local read count" numbers on tables which do not utilize SASI.
Would greatly appreciate any thoughts,
Thanks
Hi,
Can you please let me know where I can get Cassandra 3.10 RPM? If its not
available, instruction to build it would be helpful.
--
Regards,
Mahesh Rajamani
On 04/03/2017 02:58 PM, mahesh rajamani wrote:
> Hi,
>
> Can you please let me know where I can get Cassandra 3.10 RPM? If its
> not available, instruction to build it would be helpful.
Check out the 'cassandra-3.10' tag and follow the README instructions in
the redhat/ directory.
https://github
Hi,
I am trying to generate a random value of certain length and use that as one
of the value in CQL3. Below is an example
INSERT INTO "KS"."CF" (key, column1, value) VALUES
(613462303431313435313838306530667c6263317431756331, 2633174317563312f6f36,
blobAsUuid(timeuuidAsBlob(now())) + 1000);
16 Gig heap, with G1. Pertinent info from jvm.options below (we’re using
m2.2xlarge instances in AWS):
#
# HEAP SETTINGS #
#
# Heap size is automatically calculated by cassandra-env based on this
# formula: max(min(1/2 ram, 1024MB), min(1/4 ram, 8GB))
# That is:
You may have better luck switching to G1GC and using a much larger
heap (16 to 30GB). 4GB is likely too small for your amount of data,
especially if you have a lot of sstables. Then try increasing
file_cache_size_in_mb further.
Cheers,
Mark
On Tue, Mar 28, 2017 at 3:01 AM, Mokkapati, Bhargav (Nok
On 2017-04-03 12:42 (-0700), Voytek Jarnot wrote:
> Continuing to grasp at straws...
>
> Is it possible that indexing is modifying the read path such that the
> tablestats/tablehistograms output is no longer trustworthy? I notice more
> realistic "local read count" numbers on tables which do
On 2017-04-02 11:27 (-0700), Pranay akula wrote:
> where can we check gossip information of a node ?? I couldn't find
> anything in System keyspace.
>
> Is it possible to update or refresh Gossiping information on a node without
> restarting. Does enabling and disabling Gossip will help to r
Hi,
we've seen G1GC going OOM on production clusters (repeatedly) with a 16GB
heap when the workload is intense, and given you're running on m4.2xl I
wouldn't go over 16GB for the heap.
I'd suggest to revert back to CMS, using a 16GB heap and up to 6GB of new
gen. You can use 5 as MaxTenuringThre
13 matches
Mail list logo
