Unsubscribe

Please unsubscribe from this list Thanks Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 [http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif] We empower journeys of pe

TTL on UDT

When I run the command 'select ttl(udt_field) from table; I'm getting an error 'InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot use selection function ttl on collections"'. How can I get the TTL from a UDT field? Mark Furlong [cid:image001.png@01D5A92

Alter table

Why would I want to use alter table vs upserts with the new document format? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.com/mars/email/shared-ic

RE: Node failure

available. Modern client drivers also have ways to “downgrade” the CL of requests, in case they fail. E.g. for the Java driver: http://docs.datastax.com/en/latest-java-driver-api/com/datastax/driver/core/policies/DowngradingConsistencyRetryPolicy.html Thomas From: Mark Furlong [mailto:mfurl

RE: Node failure

fails, you may lose data that hasn't made it to other nodes. On Fri, Oct 6, 2017 at 10:28 AM, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: The only time I’ll have a problem is if I have a do a read all or write all. Any other gotchas I should be aware of

RE: Node failure

(so we can tell you whether or not you're likely to lose data in this process), so I'm not giving step-by-steps here because it's not very straight forward and there are a lot of caveats. On Fri, Oct 6, 2017 at 10:20 AM, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com&g

RE: Node failure

You replace it with a new node and bootstraping happens.The new node receives data from other two nodes. Rest depends on the scenerio u are asking for. Regards Akshit Jain B-Tech,2013124 9891724697 [Image removed by sender.] On Fri, Oct 6, 2017 at 10:50 PM, Mark Furlong <mfurl...@ancestry.

Node failure

What happens when I have a 3 node cluster with RF 3 and a node fails that needs to be removed? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.co

RE: Cassandra downgrade of 2.1.15 to 2.1.12

/2017 06:29 PM, Mark Furlong wrote: > I have a requirement to test a downgrade of 2.1.15 to 2.1.12. Can > someone please identify how to achieve this? Downgrades have never been officially supported, but this is a relatively small step. Testing it out is definitely a good thing. Since pro

Cassandra downgrade of 2.1.15 to 2.1.12

I have a requirement to test a downgrade of 2.1.15 to 2.1.12. Can someone please identify how to achieve this? Thanks, Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043

RE: Manual repair not showing in the log.

compaction running in nodetool compactionstats? On 7 Sep 2017 7:56 pm, "Mark Furlong" <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: I have started a repair and I received the message ‘Starting repair command #1, repairing 25301 ranges for keyspace x (para

Manual repair not showing in the log.

column family in the keyspace… nothing. The repair appears to not be doing anything, what is it stuck on? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043

RE: Invalid Gossip generation

ira/browse/CASSANDRA-10969>). On Thu, Aug 31, 2017 at 5:52 AM, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: I have a 2.1.12 cluster and have experienced an invalid gossip generation error on one of the nodes. We have tried altering the local genera

Invalid Gossip generation

is to upgrade this cluster to a new version of 2.1. In the meantime is there any other way then the above mentioned to get this node communicating with the cluster? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115

Rack Awareness

to identify the racks by the rack value or by the ip address? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]

RE: Restarting an existing node hangs

:20 AM, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: I had an existing node go down. I don’t know the cause of this. I am starting Cassandra and I can see in the log that it starts and then hangs on the opening of an sstable. Is there anything I can do

Restarting an existing node hangs

I had an existing node go down. I don’t know the cause of this. I am starting Cassandra and I can see in the log that it starts and then hangs on the opening of an sstable. Is there anything I can do to fix the sstable? I’m on OSC 2.1.12. Thanks in advance, Mark Furlong Sr. Database

RE: Repair on system_auth

tatus via nodetool netstats to kill the repair job, restart the instance On Thursday, July 6, 2017, 1:09:42 PM PDT, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: I have started a repair on my system_auth keyspace. The repair has started and the process s

Repair on system_auth

I have started a repair on my system_auth keyspace. The repair has started and the process shows as running with ps but am not seeing any CPU with top. I’m also note seeing any antientropy sessions building merkle trees in the log. Can I safely kill a repair and how? Mark Furlong Sr

Re-adding Decommissioned node

as ‘UN’ instead of ‘UJ’. Why is this? It has no data. Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]

Manual Repairs

Can a repair be paused, and if paused can it be restarted from the point of the pause, or does it start over? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043

Adding nodes and cleanup

I have added a few nodes and now am running some cleanups. Can I add an additional node while these cleanups are running? What are the ramifications of doing this? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-711

RE: Stable version apache cassandra 3.X /3.0.X

I need to reduce my disk footprint, how is 3.0.14 for stability? Also, where do I find upgrade instructions and version requirements? Thanks Mark 801-705-7115 office From: Carlos Rolo [mailto:r...@pythian.com] Sent: Wednesday, May 31, 2017 11:17 AM To: Jonathan Haddad Cc:

RE: Decommissioned node cluster shows as down

To: suraj pasuparthy <suraj.pasupar...@gmail.com> Cc: Mark Furlong <mfurl...@ancestry.com>; user@cassandra.apache.org Subject: Re: Decommissioned node cluster shows as down That’s weird. I thought decommission would ultimately remove the node from the cluster because the token(s) shoul

Decommissioned node cluster shows as down

a removenode now? Thanks, Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]

RE: Repairs on 2.1.12

The repair on the DC has completed in 308 hours. What would be helpful is if anyone has a good way of monitoring a manual ‘antientropy’ repair. Thanks Mark 801-705-7115 office From: kurt greaves [mailto:k...@instaclustr.com] Sent: Thursday, May 11, 2017 1:06 AM To: Mark Furlong <mf

Repairs on 2.1.12

properly. Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 ​[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]