Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed

[Peter Reilly]

Please, how do you do this?

Peter


On Fri, May 19, 2017 at 7:13 PM, Varun Gupta  wrote:

> Yes the bugs need to be fixed, but as a work around on dev environment,
> you can enable cassandra.yaml option to override any corrupted commit log
> file.
>
>
> Thanks,
> Varun
>
> > On May 19, 2017, at 11:31 AM, Jeff Jirsa  wrote:
> >
> >
> >
> >> On 2017-05-19 08:13 (-0700), Haris Altaf  wrote:
> >> Hi All,
> >> I am using Cassandra 3.10 for my project and whenever my local windows
> >> system, which is my development environment, crashes then cassandra
> server
> >> is unable to start. I have to delete commitlog directory after every
> system
> >> crash. This is actually annoying and what's the purpose of commitlog if
> it
> >> itself gets crashed. I have uploaded the entire dump of Cassandra Server
> >> (along with logs, commitlogs, data, configs etc) at the link below.
> Kindly
> >> share its solution. I believe it needs to be fixed.
> >>
> >
> > You need to share the exact stack trace. In cassandra 3.0+, we became
> much less tolerant of surprises in commitlog state - perhaps a bit too
> aggressive, failing to start in many cases when only minor things were
> wrong. We've recently fixed a handful of these, but they may not be
> released yet for the version you're using.
> >
> >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: user-h...@cassandra.apache.org
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

Re: Is it possible to have a column which can hold any data type (for inserting as json)

[Peter Reilly]

Example:
cqlsh> use dc_god_emperor ;
cqlsh:dc_god_emperor> create table data ( id int primary key, value text ) ;
cqlsh:dc_god_emperor> insert into data JSON'{"id": 1, "value": "hello
world"}'
  ... ;
cqlsh:dc_god_emperor> select * from data;

 id | value
+-
  1 | hello world

(1 rows)

Peter

On Wed, Feb 1, 2017 at 3:06 AM, Benjamin Roth 
wrote:

> Value is defined as text column and you try to insert a double. That's
> simply not allowed
>
> Am 01.02.2017 09:02 schrieb "Rajeswari Menon" :
>
>> Given below is the sql query I executed.
>>
>>
>>
>> *insert* *into* data JSON'{
>>
>>   "id": 1,
>>
>>"address":"",
>>
>>"datatype":"DOUBLE",
>>
>>"name":"Longitude",
>>
>>"attributes":{
>>
>>   "ID":"1"
>>
>>},
>>
>>"category":"REAL",
>>
>>"value":1.390692,
>>
>>"timestamp":1485923271718,
>>
>>"quality":"GOOD"
>>
>> }';
>>
>>
>>
>> Regards,
>>
>> Rajeswari
>>
>>
>>
>> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
>> *Sent:* 01 February 2017 12:35
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: Is it possible to have a column which can hold any data
>> type (for inserting as json)
>>
>>
>>
>> You should post the whole CQL query you try to execute! Why don't you use
>> a native JSON type for your JSON data?
>>
>>
>>
>> 2017-02-01 7:51 GMT+01:00 Rajeswari Menon :
>>
>> Hi,
>>
>>
>>
>> I have a json data as shown below.
>>
>>
>>
>> {
>>
>> "address":"127.0.0.1",
>>
>> "datatype":"DOUBLE",
>>
>> "name":"Longitude",
>>
>>  "attributes":{
>>
>> "Id":"1"
>>
>> },
>>
>> "category":"REAL",
>>
>> "value":1.390692,
>>
>> "timestamp":1485923271718,
>>
>> "quality":"GOOD"
>>
>> }
>>
>>
>>
>> To store the above json to Cassandra, I defined a table as shown below
>>
>>
>>
>> *create* *table* data
>>
>> (
>>
>>   id *int* *primary* *key*,
>>
>>   address text,
>>
>>   datatype text,
>>
>>   name text,
>>
>>   *attributes* *map* < text, text >,
>>
>>   category text,
>>
>>   value text,
>>
>>   "timestamp" *timestamp*,
>>
>>   quality text
>>
>> );
>>
>>
>>
>> When I try to insert the data as JSON I got the error : *Error decoding
>> JSON value for value: Expected a UTF-8 string, but got a Double: 1.390692*.
>> The message is clear that a double value cannot be inserted to text column.
>> The real issue is that the value can be of any data type, so the schema
>> cannot be predefined. Is there a way to create a column which can hold
>> value of any data type. (I don’t want to hold the entire json as string. My
>> preferred way is to define a schema.)
>>
>>
>>
>> Regards,
>>
>> Rajeswari
>>
>>
>>
>>
>>
>> --
>>
>> Benjamin Roth
>> Prokurist
>>
>> Jaumo GmbH · www.jaumo.com
>> Wehrstraße 46 · 73035 Göppingen · Germany
>> Phone +49 7161 304880-6 <07161%203048806> · Fax +49 7161 304880-1
>> <07161%203048801>
>> AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
>>
>

Re: question on an article

[Peter Reilly]

The original article
http://techblog.netflix.com/2011/11/benchmarking-cassandra-scalability-on.html


On Mon, Oct 31, 2016 at 5:57 PM, Peter Reilly <peter.kitt.rei...@gmail.com>
wrote:

> From the article:
> java -jar stress.jar -d "144 node ids" -e ONE -n 2700 -l 3 -i 1 -t 200
> -p 7102 -o INSERT -c 10 -r
>
> The client is writing 10 columns per row key, row key randomly chosen from
> 27 million ids, each column has a key and 10 bytes of data. The total on
> disk size for each write including all overhead is about 400 bytes.
>
> Note to sure able the batching - it may be one of the parameters to
> stress.jar.
>
> Peter
>
> On Mon, Oct 31, 2016 at 4:07 PM, Kant Kodali <k...@peernova.com> wrote:
>
>> Hi Guys,
>>
>>
>> I keep reading the articles below but the biggest questions for me are as
>> follows
>>
>> 1) what is the "data size" per request? without data size it hard for me
>> to see anything sensible
>> 2) is there batching here?
>>
>> http://www.datastax.com/1-million-writes
>>
>> http://techblog.netflix.com/2014/07/revisiting-1-million-wri
>> tes-per-second.html
>>
>> Thanks!
>>
>>
>>
>>
>

Re: question on an article

[Peter Reilly]

>From the article:
java -jar stress.jar -d "144 node ids" -e ONE -n 2700 -l 3 -i 1 -t 200
-p 7102 -o INSERT -c 10 -r

The client is writing 10 columns per row key, row key randomly chosen from
27 million ids, each column has a key and 10 bytes of data. The total on
disk size for each write including all overhead is about 400 bytes.

Note to sure able the batching - it may be one of the parameters to
stress.jar.

Peter

On Mon, Oct 31, 2016 at 4:07 PM, Kant Kodali  wrote:

> Hi Guys,
>
>
> I keep reading the articles below but the biggest questions for me are as
> follows
>
> 1) what is the "data size" per request? without data size it hard for me
> to see anything sensible
> 2) is there batching here?
>
> http://www.datastax.com/1-million-writes
>
> http://techblog.netflix.com/2014/07/revisiting-1-million-
> writes-per-second.html
>
> Thanks!
>
>
>
>

Re: Migrate from Hector(unmaintained) to Astyanax for Cassandra 2.0.7, (delaying thrift to CQL migration plan) ?

[Peter Reilly]

According to the astynax blog the project will support the java-driver -
https://github.com/Netflix/astyanax/wiki/Astyanax-over-Java-Driver


On Wed, May 28, 2014 at 8:36 AM, Andrew redmu...@gmail.com wrote:

 1. Astyanax does not *officially* support 2.0, and I’m not sure what the
 future plans are for them.
 2. Thrift is deprecated but not removed.  However,
 3. It’s an open-source project based on Netflix’ internal usage of it
 (they wrote Astyanax).  There is a mailing list available for questions (
 https://groups.google.com/group/astyanax-cassandra-client) but YMMV.
 4. I understand your hesitation, but the functions you are mentioning are
 offered by Cassandra—not the driver.  You are also not *required* to use
 new features… they are just available to you now.  Depending on how you’ve
 set your DAOs up (you are using DAOs or similar, right?), it should be
 fairly simple to migrate—certainly not harder than changing client
 libraries in general.

 Personally, I was using Astyanax for a while before I wanted to update
 Cassandra to 2.x—there’s not a huge difference between it and the Datastax
 Cassandra driver.  I’m not sure what the perceived benefits of Thrift over
 the binary interface are, other than people being familiar with one over
 another.

 Andrew

 On May 28, 2014 at 7:19:52 AM, user 01 (user...@gmail.com) wrote:

 Currently I am using Hector which is no longer maintained by its
 developers. So, for the past few days I have been looking at Astyanax  to
 be fair, I think I'm just loving its API.

 For sometime now I also had a look at CQL Java driver maintained by
 Datastax but right now, I don't very much love/understand the CQL ways of
 dealing with things like wide dynamic rows, etc, may be because of the past
 few years of working with thrift based Hector API. Also I think it's not a
 really simple transition to move from thrift to CQL.

 So I am using Cassandra 2.0.7  I wanted to know:

 1. Does Astyanax(thrift based) supports Cassandra 2.0. ?
 2. *What is the future of thrift based APIs  *( specifically Astyanax) ?
 3. where do I get support for Astyanax ?
 4. Is it recommended to delay my plans to migrate from thrift to CQL 
 just use thrift based API for now?

Re: How long are expired values actually returned?

[Peter Reilly]

You need to set grace period as well.

Peter


On Thu, May 8, 2014 at 8:44 AM, Sebastian Schmidt isib...@gmail.com wrote:

 Hi,

 I'm using the TTL feature for my application. In my tests, when using a
 TTL of 5, the inserted rows are still returned after 7 seconds, and
 after 70 seconds. Is this normal or am I doing something wrong?.

 Kind Regards,
 Sebastian