Re: Re-adding Decommissioned node

Hi Mark, Please ensure that the node is not defined as seed node in the yaml. Seed nodes don't bootstrap. ThanksAnuj On Tue, Jun 27, 2017 at 9:56 PM, Mark Furlong wrote: I have a node that has been decommissioned and it showed ‘UL’, the data volume and the

Re: Hints files are not getting truncated

Hi Meg, max_hint_window_in_ms =3 hrs means that if a node is down/unresponsive for more than 3 hrs, hints would not be stored for it any further until it becomes responsive again. It should not mean that already stored hints would be truncated after 3 hours. Regarding connection timeouts

Re: Linux version update on DSE

Hi Nitan, I think it would be simpler to take one node down at a time and replace it by bringing the new node up after linux upgrade, doing same cassandra setup, using replace_address option and setting autobootstrap=false ( as data is already there). No downtime as it would be a rolling

Re: Partition range incremental repairs

Hi Chris, Using pr with incremental repairs does not make sense. Primary range repair is an optimization over full repair. If you run full repair on a n node cluster with RF=3, you would be repairing each data thrice. E.g. in a 5 node cluster with RF=3, a range may exist on node A,B and C .

Re: Partition range incremental repairs

y were taking more like 8-9 hours. As I understand it, using incremental should have sped this process up as all three sets of data on each repair job should be marked as repaired however this does not seem to be the case. Any ideas? Chris On 6 Jun 2017, at 16:08, Anuj Wadehra <anujw_2...@yahoo.co.i

Re: LWT and non-LWT mixed

Hi Daniel, What is the RF and CL for Delete?Are you using asynchronous writes?Are you firing both statements from same node sequentially?Are you firing these queries in a loop such that more than one delete and LWT is fired for same partition? I think if you have the same client executing both

Cassandra Upgrade with Different Protocol Version

Hi, I woud like to know how people are doing rolling upgrade of Casandra clustes when there is a change in native protocol version say from 2.1 to 3.11. During rolling upgrade, if client application is restarted on nodes, the client driver may first contact an upgraded Cassandra node with v4

Re: [External] Re: Whch version is the best version to run now?

We evaluated both 3.0.x and 3.11.x. +1 for 3.11.2 as we faced major performance issues with 3.0.x. We have NOT evaluated new features on 3.11.x. Anuj Sent from Yahoo Mail on Android On Tue, 6 Mar 2018 at 19:35, Alain RODRIGUEZ wrote: Hello Tom, It's good to hear this

Re: Upgrade to v3.11.3

Hi Shalom, Just a suggestion. Before upgrading to 3.11.3 make sure you are not impacted by any open crtitical defects especially related to RT which may cause data loss e.g.14861. Please find my response below: The upgrade process that I know of is from 2.0.14 to 2.1.x (higher than 2.1.9 I

ApacheCon Europe 2019

Hi, Do we have any plans for dedicated Apache Cassandra track or sessions at ApacheCon Berlin in Oct 2019? CFP closes 26 May, 2019. ThanksAnuj Wadehra

<    1   2   3