good point! *Tamar Fraenkel * Senior Software Engineer, TOK Media
[image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 On Thu, May 23, 2013 at 2:25 PM, <moshe.kr...@barclays.com> wrote: > (Probably will not solve your problem, but worth mentioning): It’s not > enough to check that the clocks of all the servers are synchronized – I > believe that the client node sets the timestamp for a record being written. > So, you should also check the timestamp on your Hector client nodes.**** > > ** ** > > *From:* Tamar Fraenkel [mailto:ta...@tok-media.com] > *Sent:* Thursday, May 23, 2013 2:17 PM > *To:* user@cassandra.apache.org > *Subject:* Re: column with TTL of 10 seconds lives very long...**** > > ** ** > > Hi! > > TTL was set: > > [default@HLockingManager] get > HLocks['/LockedTopic/31a30c12-652d-45b3-9ac2-0401cce85517']; > => (column=69b057d4-3578-4326-a9d9-c975cb8316d2, > value=36396230353764342d333537382d343332362d613964392d633937356362383331366432, > timestamp=1369307815049000, ttl=10) > > **** > > Also, all other lock columns expire as expected.**** > > Thanks, > Tamar**** > > > **** > > *Tamar Fraenkel * > Senior Software Engineer, TOK Media **** > > [image: Inline image 1]**** > > > ta...@tok-media.com > Tel: +972 2 6409736 > Mob: +972 54 8356490 > Fax: +972 2 5612956 **** > > ** ** > > ** ** > > ** ** > > On Thu, May 23, 2013 at 1:58 PM, <moshe.kr...@barclays.com> wrote:**** > > Maybe you didn’t set the TTL correctly.**** > > Check the TTL of the column using CQL, e.g.:**** > > SELECT TTL (colName) from colFamilyName WHERE <condition>;**** > > **** > > *From:* Felipe Sere [mailto:felipe.s...@1und1.de] > *Sent:* Thursday, May 23, 2013 1:28 PM > *To:* user@cassandra.apache.org > *Subject:* AW: column with TTL of 10 seconds lives very long...**** > > **** > > This is interesting as it might affect me too :) > I have been observing deadlocks with HLockManagerImpl which dont get > resolved for a long time > even though the columns with the locks should only live for about 5-10secs. > > Any ideas how to investigate this further from the Cassandra-side?**** > ------------------------------ > > *Von:* Tamar Fraenkel [ta...@tok-media.com] > *Gesendet:* Donnerstag, 23. Mai 2013 11:58 > *An:* user@cassandra.apache.org > *Betreff:* Re: column with TTL of 10 seconds lives very long...**** > > Thanks for the response. > Running date simultaneously on all nodes (using parallel ssh) shows that > they are synced.**** > > Tamar**** > > > **** > > *Tamar Fraenkel * > Senior Software Engineer, TOK Media **** > > [image: Inline image 1]**** > > > ta...@tok-media.com > Tel: +972 2 6409736 > Mob: +972 54 8356490 > Fax: +972 2 5612956 **** > > **** > > **** > > **** > > On Thu, May 23, 2013 at 12:29 PM, Nikolay Mihaylov <n...@nmmm.nu> wrote:** > ** > > Did you synchronized the clocks between servers?**** > > **** > > On Thu, May 23, 2013 at 9:32 AM, Tamar Fraenkel <ta...@tok-media.com> > wrote:**** > > Hi! > I have Cassandra cluster with 3 node running version 1.0.11.**** > > I am using Hector HLockManagerImpl, which creates a keyspace named > HLockManagerImpl and CF HLocks.**** > > For some reason I have a row with single column that should have expired > yesterday who is still there. > I tried deleting it using cli, but it is stuck... > Any ideas how to delete it?**** > > Thanks,**** > > > **** > > *Tamar Fraenkel * > Senior Software Engineer, TOK Media **** > > [image: Inline image 1]**** > > > ta...@tok-media.com > Tel: +972 2 6409736 > Mob: +972 54 8356490 > Fax: +972 2 5612956 **** > > **** > > **** > > **** > > **** > > _______________________________________________**** > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer.**** > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary > from Barclays Sales and/or Trading, who are active market participants; and > in respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com.**** > > _______________________________________________**** > > ** ** > > _______________________________________________ > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary > from Barclays Sales and/or Trading, who are active market participants; and > in respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com. > > _______________________________________________ >
<<image001.png>>
<<tokLogo.png>>
