Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55AFC18F27 for ; Mon, 5 Oct 2015 07:02:13 +0000 (UTC) Received: (qmail 34789 invoked by uid 500); 5 Oct 2015 07:02:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 34755 invoked by uid 500); 5 Oct 2015 07:02:10 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 34745 invoked by uid 99); 5 Oct 2015 07:02:10 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2015 07:02:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 34DB8C2535 for ; Mon, 5 Oct 2015 07:02:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.28 X-Spam-Level: *** X-Spam-Status: No, score=3.28 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id hpwtof4aECEg for ; Mon, 5 Oct 2015 07:02:03 +0000 (UTC) Received: from mx-relay10.cloudservice.ag (mx-relay10.cloudservice.ag [81.20.94.213]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 8E506201F9 for ; Mon, 5 Oct 2015 07:02:02 +0000 (UTC) Received: from fw1.hostedoffice.ag ([81.20.90.82]) by mx-gate10.cloudservice.ag; Mon, 05 Oct 2015 09:01:56 +0200 Received: from EX10HUB4.hosting.inetserver.de (unknown [10.20.10.72]) by qhexrelay1.hosting.inetserver.de (Postfix) with ESMTP id A081D175D3F for ; Mon, 5 Oct 2015 09:01:55 +0200 (CEST) Received: from EX10MBOX1J.hosting.inetserver.de ([fe80::1ce9:ea19:23c1:316b]) by EX10HUB4.hosting.inetserver.de ([fe80::6dde:cf93:74ab:89ac%11]) with mapi id 14.03.0235.001; Mon, 5 Oct 2015 09:01:55 +0200 From: Daniel Stucky To: "user@cassandra.apache.org" Subject: Strange behavior of timestamp column Thread-Topic: Strange behavior of timestamp column Thread-Index: AdD/O5ynb+uwaumrT1WVgU66dFYsWA== Date: Mon, 5 Oct 2015 07:01:49 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [31.13.170.4] x-exclaimer-md-config: e299f49b-79fd-4cde-afcd-99df35de8a6e x-hostedoffice-tnef: done Content-Type: multipart/alternative; boundary="_000_B67A6EB75A6A204480574E9563D09CD58920DF61EX10MBOX1Jhosti_" MIME-Version: 1.0 X-cloud-security-sender: daniel.stucky@empolis.com X-cloud-security-recipient: user@cassandra.apache.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-gate10 with AD33A1490001 X-cloud-security-connect: fw1.hostedoffice.ag[81.20.90.82], TLS=0, IP=81.20.90.82 X-cloud-security: scantime:.5020 --_000_B67A6EB75A6A204480574E9563D09CD58920DF61EX10MBOX1Jhosti_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, we have a very simple cassandra table that contains just a single row. We h= ave a 3-machine cluster using Cassandra 2.1.8, cqlsh 5.0.1. I do the following: CREATE TABLE IF NOT EXISTS scheduler_config (name text, suspended boolean,= modified_ts timestamp, last_scheduled_start_ts timestamp, last_triggered_s= tart_ts timestamp, PRIMARY KEY((name))); INSERT INTO scheduler_config (name, last_scheduled_start_ts) VALUES('sched= uler', '2015-01-01T00:00:00.000Z'); Now I do some select * on the table and always receive the same value for = last_scheduled_start_ts that was inserted ('2015-01-01T00:00:00.000Z'). After 30-60 seconds the select * statement suddenly returns the current tim= estamp (e.g. '2015-10-05T09:00:00.000Z' )instead of the inserted value. Future select * requests also return this value ('2015-10-05T09:00:00.000Z'= ), so the timestamp does change once but not with every request. - If I insert the initial value again, the same happens. - If I insert another value (in the past), the same happens. - Droping and recreating the table does not change anything - Repairing the table also has no effect On the other hand - If I insert a value in the future (e.g. 2016) the inserted value= is always returned. - If I set the second timestamp column, the inserted value for tha= t column is always returned. - If I add a second row, the inserted value for both rows are alwa= ys returned. This behavior is really strange and seems to come from Cassandra itself (no= active client besides cqlsh). As far as we can tell this behavior started to occur on September 30th 18:0= 0:00 +0200 (not sure i fit was so from the beginning, at least we did not n= otice this effect). Before this time was a cassandra restart, as we increased server side timeo= uts. Anybody any idea what is causing this problem ? Thanks, Daniel --_000_B67A6EB75A6A204480574E9563D09CD58920DF61EX10MBOX1Jhosti_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

we have a very simple cassandra table that contains = just a single row. We have a 3-machine cluster using Cassandra 2.1.8, cqlsh= 5.0.1.

 

I do the following:

 

CREATE TABLE IF NOT EXISTS  scheduler_config (n= ame text, suspended boolean, modified_ts timestamp, last_scheduled_start_ts= timestamp, last_triggered_start_ts timestamp, PRIMARY KEY((name)));

INSERT INTO  scheduler_config (name, last_sched= uled_start_ts) VALUES('scheduler', '2015-01-01T00:00:00.000Z');<= /p>

 

Now I do some select * on the table and always recei= ve the same value for  last_scheduled_start_ts that was inserted ('201= 5-01-01T00:00:00.000Z‘).

After 30-60 seconds the select * statement suddenly = returns the current timestamp (e.g. '2015-10-05T09:00:00.000Z' )instead of = the inserted value.

Future select * requests also return this value ('20= 15-10-05T09:00:00.000Z'), so the timestamp does change once but not with ev= ery request.

 

-     &= nbsp;    If I insert the initial value again, the same happe= ns.

-     &= nbsp;    If I insert another value (in the past), the same h= appens.

-     &= nbsp;    Droping and recreating the table does not change an= ything

-     &= nbsp;    Repairing the table also has no effect

 

 

On the other hand

-     &= nbsp;    If I insert a value in the future (e.g. 2016) the i= nserted value is always returned.

-     &= nbsp;    If I set the second timestamp column, the inserted = value for that column is always  returned.

-     &= nbsp;    If I add a second row, the inserted value for both = rows are always returned.

 

This behavior is really strange and seems to come fr= om Cassandra itself (no active client besides cqlsh).

 

As far as we can tell this behavior started to occur= on September 30th 18:00:00 +0200 (not sure i fit was so from the begin= ning, at least we did not notice this effect).

Before this time was a cassandra restart, as we incr= eased server side timeouts.

 

 

Anybody any idea what is causing this problem ?=

 

Thanks,

Daniel

 

--_000_B67A6EB75A6A204480574E9563D09CD58920DF61EX10MBOX1Jhosti_--