Hi,
I want to know the actual advantage of using incremental backup.
I've read through the DataStax document and it says the merit of using
incremental backup is as follows:
- It allows storing backups offsite without transferring entire snapshots
- With incremental backups and snapshots, it can
Hi Romain,
No, I don't think we upgraded cassandra version or changed any of
those schema elements. After I realized this high load issue, I found
that some of the tables have a shorter gc_grace_seconds(1day) than the
rest and because it seemed causing constant compaction cycles, I have
changed th
Just thought I'd share this big milestone for all Cassandra users!
https://news.ycombinator.com/item?id=12089272
we use datadog (metrics emitted as raw statsd) for the dashboard. All
repair & compaction is done via blender & serf[1].
[1]https://github.com/pagerduty/blender
On Wed, Jul 13, 2016 at 2:42 PM, Kevin O'Connor wrote:
> Now that OpsCenter doesn't work with open source installs, are there any
> ru
Now that OpsCenter doesn't work with open source installs, are there any
runs at an open source equivalent? I'd be more interested in looking at
metrics of a running cluster and doing other tasks like managing
repairs/rolling restarts more so than historical data.
Hi Anuj
From
https://docs.datastax.com/en/latest-upgrade/upgrade/cassandra/upgrdBestPractCassandra.html
:
>- Employ a continual upgrade strategy for each year. Upgrades are
>impacted by the version you are upgrading from and the version you are
>upgrading to. The greater the gap betw
Did you upgrade from a previous version? DId you make some schema changes like
compaction strategy, compression, bloom filter, etc.?What about the R/W
requests? SharedPool Workers are... shared ;-) Put logs in debug to see some
examples of what services are using this pool (many actually).
Bes
Thanks a lot for suggestion Romain, I have done the setup to see the driver
logs, but haven't seen that error again.
Also thanks for the MaxRequestPerConnection tip, I will change it to 32K.
Regards,
Abhinav
On Wed, Jul 13, 2016 at 1:02 PM Romain Hardouin wrote:
> Put the driver logs in debug m
Same behavior here with a very different setup.After an upgrade to 2.1.14 (from
2.0.17) I see a high load and many NTR "all time blocked". Offheap memtable
lowered the blocked NTR for me, I put a comment on CASSANDRA-11363
Best,
Romain
Le Mercredi 13 juillet 2016 20h18, Yuan Fang a
écrit
Hi Patrick,
In fact I couldn't see any thread pool named "shared".
here is the result of tpstats from one of my nodes.
Pool NameActive Pending Completed Blocked
All time blocked
MutationStage 0 0 173237609 0
0
Put the driver logs in debug mode to see what's happen.Btw I am surprised by
the few requests by connections in your setup:
.setConnectionsPerHost(HostDistance.LOCAL, 20, 20)
.setMaxRequestsPerConnection(HostDistance.LOCAL, 128) It looks like a
protocol v2 settings (Cassandra 2.0
Dear Apache Enthusiast,
As you are no doubt already aware, we will be holding ApacheCon in
Seville, Spain, the week of November 14th, 2016. The call for papers
(CFP) for this event is now open, and will remain open until
September 9th.
The event is divided into two parts, each with its own CFP. T
Sometimes, the Pending can change from 128 to 129, 125 etc.
On Wed, Jul 13, 2016 at 10:32 AM, Yuan Fang wrote:
> $nodetool tpstats
>
> ...
> Pool Name Active Pending Completed
> Blocked All time blocked
> Native-Transport-Requests 128 128
In addition, it seems the compaction is very often. It happens like every
couple of seconds and one after one. It seems causing high load.
On Wed, Jul 13, 2016 at 10:32 AM, Yuan Fang wrote:
> $nodetool tpstats
>
> ...
> Pool Name Active Pending Completed
> Block
$nodetool tpstats
...
Pool Name Active Pending Completed
Blocked All time blocked
Native-Transport-Requests 128 1281420623949 1
142821509
...
What is this? Is it normal?
On Tue, Jul 12, 2016 at 3:03 PM, Yuan Fang wrote:
On Wed, Jul 13, 2016 at 11:32 AM, Anuj Wadehra
wrote:
> Why do you think that skipping 2.2 is not recommended when NEWS.txt
> suggests otherwise? Can you elaborate?
We test upgrading from 2.1 -> 3.x and upgrading from 2.2 -> 3.x
equivalently. There should not be a difference in terms of how we
Hi Alain,
This caught my attention:
"Also I am not sure if the 2.2 major version is something you can skip while
upgrading through a rolling restart. I believe you can, but it is not what is
recommended."
Why do you think that skipping 2.2 is not recommended when NEWS.txt suggests
otherwise? Ca
Might be more clear looking at nodetool tpstats
>From there you can see all the thread pools and if there are any blocks.
Could be something subtle like network.
On Tue, Jul 12, 2016 at 3:23 PM, Aoi Kadoya wrote:
> Hi,
>
> I am running 6 nodes vnode cluster with DSE 4.8.1, and since few weeks
>
If a node is down in my cluster.
Is it possible to exclude him from the repair process in order to continue
with the repair?
If not
Is the repair continue reparing the other replicas even if one is down?
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
As for Achilles, no I start Cassandra in the same JVM. It is meant to be
used for testing purpose only. I also faced dependency issue with different
version of Guava so I excluded the Guava pulled by the Datastax Java driver
to use the one pulled by C* itself:
https://github.com/doanduyhai/Achilles
Do either cassandra-unit or Achilles fork Cassandra to a separate JVM?
Guava libraries create a dependency hell with our current use of Hector's
embedded server. We're starting to migrate to the Datastax Java driver
with yet another guava version. I know Farsandra supports forking, so that
was wh
21 matches
Mail list logo
