Also, I see this issue only when I have more columnfamilies. looks like be
number of vnodes * number of CF combination.
does anyone have any idea on this?
On Tue, Oct 23, 2018 at 9:48 AM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Did anyone run into similar issues?
>
> On Thu, Se
Did anyone run into similar issues?
On Thu, Sep 6, 2018 at 10:27 AM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Here is the stacktrace from the failure, it looks like it's trying to
> gather all the columfamily metrics and going OOM. Is this just for the JMX
> metrics?
>
>
> https
Here is the stacktrace from the failure, it looks like it's trying to
gather all the columfamily metrics and going OOM. Is this just for the JMX
metrics?
https://github.com/apache/cassandra/blob/cassandra-2.1.16/src/java/org/apache/cassandra/metrics/ColumnFamilyMetrics.java
ERROR [MessagingServic
thank you
On Thu, Aug 30, 2018 at 11:58 AM Jeff Jirsa wrote:
> This is the closest JIRA that comes to mind (from memory, I didn't search,
> there may be others): https://issues.apache.org/jira/browse/CASSANDRA-8150
>
> The best blog that's all in one place on tuning GC in cassandra is
> actually
This is the closest JIRA that comes to mind (from memory, I didn't search,
there may be others): https://issues.apache.org/jira/browse/CASSANDRA-8150
The best blog that's all in one place on tuning GC in cassandra is actually
Amy's 2.1 tuning guide:
https://tobert.github.io/pages/als-cassandra-21-
Hi Jeff,
Is there any JIRA that talks about increasing the HEAP will help?
Also, any other alternatives than increasing the HEAP Size? last time when
I tried increasing the heap, longer GC Pauses caused more damage in terms
of latencies while gc pause.
On Wed, Aug 29, 2018 at 11:07 PM Jai Bheemse
okay, thank you
On Wed, Aug 29, 2018 at 11:04 PM Jeff Jirsa wrote:
> You’re seeing an OOM, not a socket error / timeout.
>
> --
> Jeff Jirsa
>
>
> On Aug 29, 2018, at 10:56 PM, Jai Bheemsen Rao Dhanwada <
> jaibheem...@gmail.com> wrote:
>
> Jeff,
>
> any idea if this is somehow related to :
> ht
You’re seeing an OOM, not a socket error / timeout.
--
Jeff Jirsa
> On Aug 29, 2018, at 10:56 PM, Jai Bheemsen Rao Dhanwada
> wrote:
>
> Jeff,
>
> any idea if this is somehow related to :
> https://issues.apache.org/jira/browse/CASSANDRA-11840?
> does increasing the value of streaming_soc
CMS is fine at 12G for sure, likely up to 16G
You’ll want to initiate CMS a bit earlier (55-69%), and you likely want new gen
to be larger - perhaps 3-6G
You’ll want to manually set the memtable size - it scales with heap by default
After bootstrap you can lower it again
--
Jeff Jirsa
> O
Jeff,
any idea if this is somehow related to :
https://issues.apache.org/jira/browse/CASSANDRA-11840?
does increasing the value of streaming_socket_timeout_in_ms to a higher
value helps?
On Wed, Aug 29, 2018 at 10:52 PM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> I have 72 nodes
I have 72 nodes in the cluster, across 8 datacenters.. the moment I try to
increase the node above 84 or so, the issue starts.
I am still using CMS Heap, assuming it will create more harm if I increase
the heap size beyond 8G(recommended).
On Wed, Aug 29, 2018 at 6:53 PM Jeff Jirsa wrote:
> Giv
Given the size of your schema, you’re probably getting flooded with a bunch of
huge schema mutations as it hops into gossip and tries to pull the schema from
every host it sees. You say 8 DCs but you don’t say how many nodes - I’m
guessing it’s a lot?
This is something that’s incrementally be
It fails before bootstrap
streaming throughpu on the nodes is set to 400Mb/ps
On Wednesday, August 29, 2018, Jeff Jirsa wrote:
> Is the bootstrap plan succeeding (does streaming start or does it crash
> before it logs messages about streaming starting)?
>
> Have you capped the stream throughput
Is the bootstrap plan succeeding (does streaming start or does it crash before
it logs messages about streaming starting)?
Have you capped the stream throughput on the existing hosts?
--
Jeff Jirsa
> On Aug 29, 2018, at 5:02 PM, Jai Bheemsen Rao Dhanwada
> wrote:
>
> Hello All,
>
> We ar
Hello All,
We are seeing some issue when we add more nodes to the cluster, where new
node bootstrap is not able to stream the entire metadata and fails to
bootstrap. Finally the process dies with OOM (java.lang.OutOfMemoryError:
Java heap space)
But if I remove few nodes from the cluster we don't
15 matches
Mail list logo
