date:20130313

[Cassandra Wiki] Trivial Update of JIRJamiso by JIRJamiso

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The JIRJamiso page has been changed by JIRJamiso:
http://wiki.apache.org/cassandra/JIRJamiso

New page:
Hi! Throughout southern california: Hxcv F. KahqesaBR
I really like to make friends, x whatever area, d which area are you presently 
k through.BR
BR
And I also f like to browse many advertisements, ebooks. Learn about many 
fashion features of the patient.BR
Your speak to is actually:485 * 5505540BR
BR
Stop by my page - [[http://www.redwing.lib.mn.us/beatbydrdre.html|beats by dr 
dre headphones]]

[Cassandra Wiki] Trivial Update of IvysnAlfr by IvysnAlfr

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The IvysnAlfr page has been changed by IvysnAlfr:
http://wiki.apache.org/cassandra/IvysnAlfr

New page:
The CAMELIA JUSTICE is modern Conductor who has Kept many books in favor of of 
aforesaid topic.BR
He belongs to The Merry Institute of Kind Children built at Salisbury in South 
Lyon. The writer has an familiarity of 56 weeks. For more information click 
hereBR
BR
My weblog - [[http://www.fairbeatsbydre.com|monster beats]]

[jira] [Commented] (CASSANDRA-5314) Replaying old batches can 'undo' deletes

2013-03-13 Thread Sylvain Lebresne (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600936#comment-13600936
 ] 

Sylvain Lebresne commented on CASSANDRA-5314:
-

bq. We TTL hints with gcgs to prevent this

Interesting. There is 2 (somewhat conflicting) things that seems weird to me 
with that:
# the intent seems broken if gc_grace==0, since a TTL of 0 means no TTL at all.
# in the (not uncommon) case of using TTL on all columns without doing manual 
deletion, it makes sense to use a very low gc_grace. In this case, this seems 
to make hints useless, which I'm not sure is what people expect (I'll admit I 
was unaware of that).

 Replaying old batches can 'undo' deletes
 

 Key: CASSANDRA-5314
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5314
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.2
Reporter: Aleksey Yeschenko
Assignee: Aleksey Yeschenko
 Fix For: 1.2.3


 Batchlog manager does not subtract the time spent in the batchlog from hints' 
 ttls and this may cause undoing deletes. The attached patch fixes it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-3929) Support row size limits

2013-03-13 Thread Sylvain Lebresne (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600947#comment-13600947
 ] 

Sylvain Lebresne commented on CASSANDRA-3929:
-

bq. How would you use this filter interface to implement something 
CQL-row-aware?

I'm not sure honestly. I was suggesting that as a simpler alternative to 
modifying the compaction strategy API, which wouldn't be easily CQL-aware 
either because both solution involve dealing with the internal storage engine. 
Now, it would be possible to write something CQL-aware with the filter 
interface above (except maybe that we might want to provide the CFMetaData 
object too), but that would have to be done manually (typically using the 
ColumnCounter class, you could reasonably easily start dropping columns once 
you reach the nth CQL-row).

 Support row size limits
 ---

 Key: CASSANDRA-3929
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3929
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: Jonathan Ellis
Priority: Minor
  Labels: ponies
 Fix For: 2.0

 Attachments: 3929_b.txt, 3929_c.txt, 3929_d.txt, 3929_e.txt, 
 3929_f.txt, 3929_g_tests.txt, 3929_g.txt, 3929.txt


 We currently support expiring columns by time-to-live; we've also had 
 requests for keeping the most recent N columns in a row.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of GertrudeR by GertrudeR

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The GertrudeR page has been changed by GertrudeR:
http://wiki.apache.org/cassandra/GertrudeR

New page:
Nothing to write about me really.BR
Nice to be here and a part of apache.org.BR
I really wish I am useful at allBR
BR
Here is my web-site :: 
[[http://www.Eyelashextensionsreviews.co.uk/reviews/rio-eyelash-extension-kit-reviews/|rio
 Eyelash extension set]]

[jira] [Resolved] (CASSANDRA-5336) C* crashes with an OOM error when using the Simba Driver on a very wide table

2013-03-13 Thread Sylvain Lebresne (JIRA)

[
https://issues.apache.org/jira/browse/CASSANDRA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-5336.
-

Resolution: Not A Problem

bq. I think a simple select count(*) from table limit 1; will do it

If we are talking of CQL3, this is a duplicate of CASSANDRA-3702 that will be
(but is not currently) solved by CASSANDRA-4415. Namely, 'select count' has to
count everything (because we have no better way to do it) and is not paged, so
it is going to OOM if asked to count too much.

bq. It translates into a series of get_range_slice calls which bring back all
of the rows, and for every row, it brings back every single column name.

Then it means that the Simba Driver should page those get_range_slice calls
that it generates to avoid the OOM. But that's a Simba Driver bug, not a
Cassandra one.

So to sum up, we are aware that for CQL3 the COUNT may OOM because it doesn't
page and we're going to fix it in CASSANDRA-4415. But on the thrift side,
paging should be done by the client (the simba driver in that instance) and
this is likely not going to change (as for shouldn't that throw an exception
rather than OOMing?, CASSANDRA-3911 might be relevant).

C* crashes with an OOM error when using the Simba Driver on a very wide table
-

Key: CASSANDRA-5336
URL: https://issues.apache.org/jira/browse/CASSANDRA-5336
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 1.1.6
Environment: C* on a Mac with 1GB VM. Simba ODBC driver
Reporter: Steven Lowenthal
Attachments: nhanes600-10k.tarZ, thrift.in, thrift.out

The Simba driver executes a version of a count(*) query:
SELECT SUM(1) from nhanes3 having sum(1) 0. It uses this format so ODBC
returns a no rows found error if the table is empty. It translates into a
series of get_range_slice calls which bring back all of the rows, and for
every row, it brings back every single column name. C* crashes with an OOM
in the thrift code. The table has almost 600 columns of mixed text and
numeric data with many empty values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of GettingStarted by SylvainLebresne

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The GettingStarted page has been changed by SylvainLebresne:
http://wiki.apache.org/cassandra/GettingStarted?action=diffrev1=82rev2=83

  == Cassandra documentation from DataStax ==
- !DataStax's latest [[http://www.datastax.com/docs/1.1/index|Cassandra 
documentation]] covers topics from installation to troubleshooting, including a 
[[http://www.datastax.com/docs/quick_start/quickstart|Quick Start Guide]].  
Documentation for older releases is also available.
+ !DataStax's latest [[http://www.datastax.com/docs/1.2/index|Cassandra 
documentation]] covers topics from installation to troubleshooting, including a 
[[http://www.datastax.com/docs/quick_start/quickstart|Quick Start Guide]].  
Documentation for older releases is also available.
   
  == Introduction ==
  This document aims to provide a few easy to follow steps to take the 
first-time user from installation, to running single node Cassandra, and 
overview to configure multinode cluster.

[jira] [Commented] (CASSANDRA-5338) scripts fail when paths contain space

2013-03-13 Thread Amichai Rothman (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600975#comment-13600975
 ] 

Amichai Rothman commented on CASSANDRA-5338:


btw, this problem would be easily alleviated if there wasn't so much 
duplication in the scripts, some of which get updated and others forgotten... 
why not consolidate the duplication into a single master script? For backwards 
compatibility, the existing scripts can continue to exist but just call the 
master script with appropriate parameters.

 scripts fail when paths contain space
 -

 Key: CASSANDRA-5338
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5338
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2.2
 Environment: Kubuntu 12.10 (GNU bash 4.2.37), and Windows XP (msysgit 
 GNU bash 3.1.0)
Reporter: Amichai Rothman
Priority: Minor
 Attachments: fix_spaces_in_paths.patch


 The shell scripts fail when the cassandra or java dirs contain spaces.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-5340) use getopts instead of getopt in shell script

2013-03-13 Thread Amichai Rothman (JIRA)

Amichai Rothman created CASSANDRA-5340:
--

 Summary: use getopts instead of getopt in shell script
 Key: CASSANDRA-5340
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5340
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.2
 Environment: Windows XP msysgit GNU bash 3.1.0
Reporter: Amichai Rothman
Priority: Minor


I don't know what the officially supported platforms are or what versions of sh 
they support... however I do know that the cassandra startup script fails on at 
least one platform (Windows XP/msysgit) since it uses the external utility 
getopt which is not available there. Using the shell built-in getopts command 
instead, or parsing the command line manually, would fix the problem.

I'm no shell expert, but a little searching came up with the fact that the 
getopt utility is not required by POSIX (which a script comment claims needs to 
be adhered to) whereas getopts is standard and more portable. Some claim getopt 
is better when long option names need to be supported, however cassandra 
doesn't use those anyway.

Unless someone knows of a supported platform that doesn't support getopts, the 
script should be changed to use it instead of getopt. If such a platform 
exists, perhaps using neither (manually parsing args) should be considered - 
it's not too much work, and there are plenty of existing templates for doing 
this to build on, and that would provide the best portability across platforms.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster

2013-03-13 Thread Sylvain Lebresne (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylvain Lebresne updated CASSANDRA-5334:


Attachment: 5334.txt

This was introduced by CASSANDRA-4433, that removed the name column of the 
schema_keyspaces table, but that one, while redundant, is used by 1.1 nodes.

This boils down to the problem I described in CASSANDRA-4603: we cannot easily 
remove anything in the schema tables without breaking rolling upgrades.

So attaching a patch that reintroduce the name column in 1.2 (we don't use it 
but we write it for compatibility sake). 


 NullPointerException in a mixed 1.1 / 1.2 cluster
 -

 Key: CASSANDRA-5334
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
 Attachments: 5334.txt


 I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 
 node upgraded from 1.1.9. 
 The upgrade works, and I don't see any end user problems, however I see this 
 exception in the logs on the non-upgraded nodes:
 {code}
 ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java 
 (line 135) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.NullPointerException
   at 
 org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
   at 
 org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
   at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
   at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
   at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
   at 
 org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
   at 
 org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
   at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
   at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
   at 
 org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
   at 
 org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 {code}
 Steps to reproduce:
 {code}
 ccm create -v 1.1.9 1.1.9
 ccm populate -n 3
 ccm start
 ccm node1 stress
 ccm node1 down
 {code}
 edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
 {code}
 ccm node1 up
 {code}
 The cluster is now a mixed version, and works for user queries, but with the 
 exception above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster

2013-03-13 Thread Sylvain Lebresne (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylvain Lebresne updated CASSANDRA-5334:


Fix Version/s: 1.2.3

 NullPointerException in a mixed 1.1 / 1.2 cluster
 -

 Key: CASSANDRA-5334
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
 Fix For: 1.2.3

 Attachments: 5334.txt


 I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 
 node upgraded from 1.1.9. 
 The upgrade works, and I don't see any end user problems, however I see this 
 exception in the logs on the non-upgraded nodes:
 {code}
 ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java 
 (line 135) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.NullPointerException
   at 
 org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
   at 
 org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
   at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
   at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
   at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
   at 
 org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
   at 
 org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
   at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
   at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
   at 
 org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
   at 
 org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 {code}
 Steps to reproduce:
 {code}
 ccm create -v 1.1.9 1.1.9
 ccm populate -n 3
 ccm start
 ccm node1 stress
 ccm node1 down
 {code}
 edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
 {code}
 ccm node1 up
 {code}
 The cluster is now a mixed version, and works for user queries, but with the 
 exception above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5129) newly bootstrapping nodes hang indefinitely in STATUS:BOOT while JOINING cluster

2013-03-13 Thread Kristoffer Carlson (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601043#comment-13601043
 ] 

Kristoffer Carlson commented on CASSANDRA-5129:
---

I'm still experiencing this on 1.2.2. Same exception and same result. I took a 
thread dump and it didn't have anything interesting in it.

 newly bootstrapping nodes hang indefinitely in STATUS:BOOT while JOINING 
 cluster  
 --

 Key: CASSANDRA-5129
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5129
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.0
 Environment: Ubuntu 12.04
Reporter: Michael Kjellman
Assignee: Brandon Williams
 Fix For: 1.2.2


 bootstrapping a new node causes it to hang indefinitely in STATUS:BOOT
 Nodes streaming to the new node report 
 {code}
 Mode: NORMAL
  Nothing streaming to /10.8.30.16
 Not receiving any streams.
 Pool NameActive   Pending  Completed
 Commandsn/a 01843990
 Responses   n/a 2 661750
 {code}
 the node being streamed to stuck in the JOINING state reports:
 {code}
 Mode: JOINING
 Not sending any streams.
  Nothing streaming from /10.8.30.103
  Nothing streaming from /10.8.30.102
 Pool NameActive   Pending  Completed
 Commandsn/a 0 10
 Responses   n/a 0 613577
 {code}
 it appears that the nodes in the nothing streaming state never sends a 
 finished streaming to the joining node.
 no exceptions are thrown during the streaming on either node while the node 
 is in this state.
 {code:name=full gossip state of bootstrapping node}
 /10.8.30.16
   NET_VERSION:6
   RELEASE_VERSION:1.2.0
   STATUS:BOOT,127605887595351923798765477786913079289
   RACK:RAC1
   RPC_ADDRESS:0.0.0.0
   DC:DC1
   SCHEMA:5cd8420d-ce3c-3625-8293-67558a24816b
   HOST_ID:e20817ce-7454-4dc4-a1c6-b1dec35c4491
   LOAD:1.11824041581E11
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of RoccoBurn by RoccoBurn

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The RoccoBurn page has been changed by RoccoBurn:
http://wiki.apache.org/cassandra/RoccoBurn

New page:
University or college bit by bit apart around an additional, Gu school, through 
the mentor and also lessons that belongs to them tough understand, I've 
productively performed expert tutorials,, not to mention establish good 
practice of significant research not to mention perform!. Can hard-working, 
faithful and even follow the guideline db of credibility plus condition, this 
daring to help challenge his or her self together with construct their very own 
probable;BR
Help to make a dynamic human being, the project determination, in an effort to 
unique goal to undertake the situations you are looking for gravely straight 
into strength;BR
Have a very good bxec style, able to get in touch with many people, basically 
teams, might be fairly immediate verbal exchanges with folks, solid crew 
organization competencies and also a nature associated with collaboration 
individuals, be ready to actually work together to quickly attain crew 
goals;BR
Be a master at discovering, homework and additionally pragmatism, assiduously, 
own intensive interest emm as well as vibrant skills, robust ability to change, 
in for you to include into a brand-new line of business in a very amount of 
time, to adapt to the pup and set him to undertake;BR
BR
Here is my blog post - [[http://www.firmchaneloutlet.com|chanel handbags]]

[Cassandra Wiki] Trivial Update of CarmenCIA by CarmenCIA

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The CarmenCIA page has been changed by CarmenCIA:
http://wiki.apache.org/cassandra/CarmenCIA

New page:
Not much to say about myself really.BR
Great to be a part of this site.BR
I really hope Im useful at allBR
BR
Also visit my web blog - [[http://www.housebuyerenquiry.co.uk|sell your home 
fast]]

[jira] [Commented] (CASSANDRA-5336) C* crashes with an OOM error when using the Simba Driver on a very wide table

2013-03-13 Thread Jonathan Ellis (JIRA)

[
https://issues.apache.org/jira/browse/CASSANDRA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601132#comment-13601132
]

Jonathan Ellis commented on CASSANDRA-5336:
---

I guess I didn't read very carefully; I assumed that it would be using
{{get_count}} on the Thrift side, which auto-pages to avoid this problem. If
you're going to use get_range_slices, then as Sylvain says you [which is to
say, Simba] need to do your own paging to avoid OOM.

C* crashes with an OOM error when using the Simba Driver on a very wide table
-

[Cassandra Wiki] Trivial Update of MallorySc by MallorySc

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The MallorySc page has been changed by MallorySc:
http://wiki.apache.org/cassandra/MallorySc

New page:
Not much to say about me at all.BR
Finally a part of this community.BR
I really wish I'm useful at allBR
BR
My page :: 
[[http://linuxvpnrouter.com/tiki-index.php?page=UserPagemaggiewil|linuxvpnrouter.com]]

[jira] [Commented] (CASSANDRA-5202) AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... while querying data after bulk insert - 1M rows with 100 columns. Also failure to drop

2013-03-13 Thread Dan Peebles (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601202#comment-13601202
 ] 

Dan Peebles commented on CASSANDRA-5202:


I was getting the same issue and found this bug. As a workaround, I tried 
changing my testsuite to avoid dropping the keyspace each time, and simply 
truncate every CF in the keyspace instead, but that seems to lead to the same 
symptoms. Just thought I'd point that out in case the truncate code path was 
being overlooked.

 AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... 
 while querying data after bulk insert - 1M rows with 100 columns. Also 
 failure to drop column families
 

 Key: CASSANDRA-5202
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5202
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
 Environment: OS: Windows 7, 
 Server: Cassandra 1.1.9 release drop
 Client: astyanax 1.56.21, 
 JVM: Sun/Oracle JVM 64 bit (jdk1.6.0_27)
Reporter: Marat Bedretdinov
  Labels: test
 Attachments: 5202-1.1.txt, astyanax-stress-driver.zip


 Attached is a driver that sequentially:
 1. Drops keyspace
 2. Creates keyspace
 4. Creates 2 column families
 5. Seeds 1M rows with 100 columns
 6. Queries these 2 column families
 The above steps are repeated 1000 times.
 The following exception is observed at random (race - SEDA?):
 ERROR [ReadStage:55] 2013-01-29 19:24:52,676 AbstractCassandraDaemon.java 
 (line 135) Exception in thread Thread[ReadStage:55,5,main]
 java.lang.AssertionError: DecoratedKey(-1, ) != 
 DecoratedKey(62819832764241410631599989027761269388, 313a31) in 
 C:\var\lib\cassandra\data\user_role_reverse_index\business_entity_role\user_role_reverse_index-business_entity_role-hf-1-Data.db
   at 
 org.apache.cassandra.db.columniterator.SSTableSliceIterator.init(SSTableSliceIterator.java:60)
   at 
 org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:67)
   at 
 org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:79)
   at 
 org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:256)
   at 
 org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:64)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1367)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1229)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1164)
   at org.apache.cassandra.db.Table.getRow(Table.java:378)
   at 
 org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:69)
   at 
 org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:822)
   at 
 org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1271)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 This exception appears in the server at the time of client submitting a query 
 request (row slice) and not at the time data is seeded. The client times out 
 and this data can no longer be queried as the same exception would always 
 occur from there on.
 Also on iteration 201, it appears that dropping column families failed and as 
 a result their recreation failed with unique column family name violation 
 (see exception below). Note that the data files are actually gone, so it 
 appears that the server runtime responsible for creating column family was 
 out of sync with the piece that dropped them:
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5105 ms
 Iteration: 200; Total running time for 1000 queries is 232; Average running 
 time of 1000 queries is 0 ms
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5361 ms
 Iteration: 201; Total running time for 1000 queries is 222; Average running 
 time of 1000 queries is 0 ms
 Starting dropping column families
 Starting creating column families
 Exception in thread main

[jira] [Commented] (CASSANDRA-5202) AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... while querying data after bulk insert - 1M rows with 100 columns. Also failure to drop

2013-03-13 Thread Jonathan Ellis (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601213#comment-13601213
 ] 

Jonathan Ellis commented on CASSANDRA-5202:
---

bq. I don't want to embed UUID cfId to file name

It's ugly, but that's the logical solution, isn't it?  We're saying that 
sstables for table foo on Tuesday, and table foo on Wednesday after drop and 
re-create, are really different things, so distinguishing them as such on the 
FS is if nothing else a good extra layer of protection against mixing the two.

And your patch already stores cfid in the system table, so users could still 
find out which sstables belong to which table definitions, although granted 
it's not as convenient.

 AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... 
 while querying data after bulk insert - 1M rows with 100 columns. Also 
 failure to drop column families
 

 Key: CASSANDRA-5202
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5202
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
 Environment: OS: Windows 7, 
 Server: Cassandra 1.1.9 release drop
 Client: astyanax 1.56.21, 
 JVM: Sun/Oracle JVM 64 bit (jdk1.6.0_27)
Reporter: Marat Bedretdinov
  Labels: test
 Attachments: 5202-1.1.txt, astyanax-stress-driver.zip


 Attached is a driver that sequentially:
 1. Drops keyspace
 2. Creates keyspace
 4. Creates 2 column families
 5. Seeds 1M rows with 100 columns
 6. Queries these 2 column families
 The above steps are repeated 1000 times.
 The following exception is observed at random (race - SEDA?):
 ERROR [ReadStage:55] 2013-01-29 19:24:52,676 AbstractCassandraDaemon.java 
 (line 135) Exception in thread Thread[ReadStage:55,5,main]
 java.lang.AssertionError: DecoratedKey(-1, ) != 
 DecoratedKey(62819832764241410631599989027761269388, 313a31) in 
 C:\var\lib\cassandra\data\user_role_reverse_index\business_entity_role\user_role_reverse_index-business_entity_role-hf-1-Data.db
   at 
 org.apache.cassandra.db.columniterator.SSTableSliceIterator.init(SSTableSliceIterator.java:60)
   at 
 org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:67)
   at 
 org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:79)
   at 
 org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:256)
   at 
 org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:64)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1367)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1229)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1164)
   at org.apache.cassandra.db.Table.getRow(Table.java:378)
   at 
 org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:69)
   at 
 org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:822)
   at 
 org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1271)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 This exception appears in the server at the time of client submitting a query 
 request (row slice) and not at the time data is seeded. The client times out 
 and this data can no longer be queried as the same exception would always 
 occur from there on.
 Also on iteration 201, it appears that dropping column families failed and as 
 a result their recreation failed with unique column family name violation 
 (see exception below). Note that the data files are actually gone, so it 
 appears that the server runtime responsible for creating column family was 
 out of sync with the piece that dropped them:
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5105 ms
 Iteration: 200; Total running time for 1000 queries is 232; Average running 
 time of 1000 queries is 0 ms
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5361 ms
 Iteration: 201; Total running

[jira] [Commented] (CASSANDRA-5202) AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... while querying data after bulk insert - 1M rows with 100 columns. Also failure to drop

2013-03-13 Thread Jonathan Ellis (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601216#comment-13601216
 ] 

Jonathan Ellis commented on CASSANDRA-5202:
---

bq. truncate ... seems to lead to the same symptoms

I think we can fix that by recording the sstable generation somewhere, instead 
of just assuming that if no files of generation = X exist, we should start 
creating new sstables with X.

(Which I think would actually be a simpler fix for the issue in general...  but 
giving different versions of a table distinct IDs is the Right Solution, so 
I'm still +1 on that unless Yuki thinks the cost is too high for the practical 
benefits.)

 AssertionError in the backend: DecoratedKey(-1, ) != DecoratedKey(x, y) ... 
 while querying data after bulk insert - 1M rows with 100 columns. Also 
 failure to drop column families
 

 Key: CASSANDRA-5202
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5202
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
 Environment: OS: Windows 7, 
 Server: Cassandra 1.1.9 release drop
 Client: astyanax 1.56.21, 
 JVM: Sun/Oracle JVM 64 bit (jdk1.6.0_27)
Reporter: Marat Bedretdinov
  Labels: test
 Attachments: 5202-1.1.txt, astyanax-stress-driver.zip


 Attached is a driver that sequentially:
 1. Drops keyspace
 2. Creates keyspace
 4. Creates 2 column families
 5. Seeds 1M rows with 100 columns
 6. Queries these 2 column families
 The above steps are repeated 1000 times.
 The following exception is observed at random (race - SEDA?):
 ERROR [ReadStage:55] 2013-01-29 19:24:52,676 AbstractCassandraDaemon.java 
 (line 135) Exception in thread Thread[ReadStage:55,5,main]
 java.lang.AssertionError: DecoratedKey(-1, ) != 
 DecoratedKey(62819832764241410631599989027761269388, 313a31) in 
 C:\var\lib\cassandra\data\user_role_reverse_index\business_entity_role\user_role_reverse_index-business_entity_role-hf-1-Data.db
   at 
 org.apache.cassandra.db.columniterator.SSTableSliceIterator.init(SSTableSliceIterator.java:60)
   at 
 org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:67)
   at 
 org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:79)
   at 
 org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:256)
   at 
 org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:64)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1367)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1229)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1164)
   at org.apache.cassandra.db.Table.getRow(Table.java:378)
   at 
 org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:69)
   at 
 org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:822)
   at 
 org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1271)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 This exception appears in the server at the time of client submitting a query 
 request (row slice) and not at the time data is seeded. The client times out 
 and this data can no longer be queried as the same exception would always 
 occur from there on.
 Also on iteration 201, it appears that dropping column families failed and as 
 a result their recreation failed with unique column family name violation 
 (see exception below). Note that the data files are actually gone, so it 
 appears that the server runtime responsible for creating column family was 
 out of sync with the piece that dropped them:
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5105 ms
 Iteration: 200; Total running time for 1000 queries is 232; Average running 
 time of 1000 queries is 0 ms
 Starting dropping column families
 Dropped column families
 Starting dropping keyspace
 Dropped keyspace
 Starting creating column families
 Created column families
 Starting seeding data
 Total rows inserted: 100 in 5361 ms
 Iteration: 201; Total running time for 1000 queries is 222; Average running

[jira] [Created] (CASSANDRA-5341) Select writetime Exception when data doesn't exist

2013-03-13 Thread julien campan (JIRA)

julien campan created CASSANDRA-5341:


 Summary: Select writetime  Exception when  data doesn't exist
 Key: CASSANDRA-5341
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5341
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 1.2.2
Reporter: julien campan
Priority: Minor


Hi,

When I try do to a “select writetime” on a empty column, I have an Exception. 
For example : 
Create table test (id  int, value int, value2 int, primary key (id));   
INSERT INTO test (id, value ) VALUES ( 1,100) ;

select * from test where id =1; 
==
 id | value | value2
+---+
  1 |   100 |   null

It’s working.

select WRITETIME(value) from test where id =1; 
==
 writetime(value)
--
 1363184789539000
It’s working


select WRITETIME(value2) from test where id =1; 

==TSocket read 0 bytes

I have an Exception.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5338) scripts fail when paths contain space

2013-03-13 Thread Brandon Williams (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5338:


Reviewer: urandom

 scripts fail when paths contain space
 -

 Key: CASSANDRA-5338
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5338
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2.2
 Environment: Kubuntu 12.10 (GNU bash 4.2.37), and Windows XP (msysgit 
 GNU bash 3.1.0)
Reporter: Amichai Rothman
Priority: Minor
 Attachments: fix_spaces_in_paths.patch


 The shell scripts fail when the cassandra or java dirs contain spaces.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5338) scripts fail when paths contain space

2013-03-13 Thread Brandon Williams (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601239#comment-13601239
 ] 

Brandon Williams commented on CASSANDRA-5338:
-

See CASSANDRA-5301 for the duplication.

 scripts fail when paths contain space
 -

 Key: CASSANDRA-5338
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5338
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2.2
 Environment: Kubuntu 12.10 (GNU bash 4.2.37), and Windows XP (msysgit 
 GNU bash 3.1.0)
Reporter: Amichai Rothman
Priority: Minor
 Attachments: fix_spaces_in_paths.patch


 The shell scripts fail when the cassandra or java dirs contain spaces.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of Basil27I by Basil27I

2013-03-13 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Basil27I page has been changed by Basil27I:
http://wiki.apache.org/cassandra/Basil27I

New page:
Hi! I'm michael duivis: Nwhr S. CxxtubcBR
I connect with others, v no matter what nation, n the specific area are you 
feeling p because of.BR
I g wish to examine a lot of fashion magazines, publications. Study a few vogue 
portions of the patient.BR
This communication might be:291 * 0255432BR
BR
My webpage ... [[http://www.packchaneloutlet.com|chanel outlet]]

1 2 >

1 - 100 of 103 matches

Mail list logo