[jira] [Commented] (CASSANDRA-5818) Duplicated error messages on directory creation error at startup
[
https://issues.apache.org/jira/browse/CASSANDRA-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751055#comment-13751055
]
Sylvain Lebresne commented on CASSANDRA-5818:
-
Honestly, I think we've been looking at that issue the wrong way. I don't think
we should do anything with the general logging here (and I'm -1 on
DuplicateMessageFilter given how it works).
What we should do is, in the code that creates the directories at startup, add
a check for permissions on the data directory (the same could be done for the
commitlog directory btw) that stops startup right away with just one message
(which would be more friendly as it would tell what's the problem). On top of
that, if we really want to be thorough, we could try creating the data
directory first (if it doesn't exist already) and check for errors, and then
create the CF directories (instead of trying to create all the CF directories
upfront and logging a message for each one when the problem is actually on the
top-level data directory).
Duplicated error messages on directory creation error at startup
Key: CASSANDRA-5818
URL: https://issues.apache.org/jira/browse/CASSANDRA-5818
Project: Cassandra
Issue Type: Bug
Reporter: Michaël Figuière
Assignee: Aleksey Yeschenko
Priority: Trivial
Fix For: 2.1
When I start Cassandra without the appropriate OS access rights to the
default Cassandra directories, I get a flood of {{ERROR}} messages at
startup, whereas one per directory would be more appropriate. See bellow:
{code}
ERROR 13:37:39,792 Failed to create
/var/lib/cassandra/data/system/schema_triggers directory
ERROR 13:37:39,797 Failed to create
/var/lib/cassandra/data/system/schema_triggers directory
ERROR 13:37:39,798 Failed to create
/var/lib/cassandra/data/system/schema_triggers directory
ERROR 13:37:39,798 Failed to create
/var/lib/cassandra/data/system/schema_triggers directory
ERROR 13:37:39,799 Failed to create
/var/lib/cassandra/data/system/schema_triggers directory
ERROR 13:37:39,800 Failed to create /var/lib/cassandra/data/system/batchlog
directory
ERROR 13:37:39,801 Failed to create /var/lib/cassandra/data/system/batchlog
directory
ERROR 13:37:39,801 Failed to create /var/lib/cassandra/data/system/batchlog
directory
ERROR 13:37:39,802 Failed to create /var/lib/cassandra/data/system/batchlog
directory
ERROR 13:37:39,802 Failed to create
/var/lib/cassandra/data/system/peer_events directory
ERROR 13:37:39,803 Failed to create
/var/lib/cassandra/data/system/peer_events directory
ERROR 13:37:39,803 Failed to create
/var/lib/cassandra/data/system/peer_events directory
ERROR 13:37:39,804 Failed to create
/var/lib/cassandra/data/system/compactions_in_progress directory
ERROR 13:37:39,805 Failed to create
/var/lib/cassandra/data/system/compactions_in_progress directory
ERROR 13:37:39,805 Failed to create
/var/lib/cassandra/data/system/compactions_in_progress directory
ERROR 13:37:39,806 Failed to create
/var/lib/cassandra/data/system/compactions_in_progress directory
ERROR 13:37:39,807 Failed to create
/var/lib/cassandra/data/system/compactions_in_progress directory
ERROR 13:37:39,808 Failed to create /var/lib/cassandra/data/system/hints
directory
ERROR 13:37:39,809 Failed to create /var/lib/cassandra/data/system/hints
directory
ERROR 13:37:39,809 Failed to create /var/lib/cassandra/data/system/hints
directory
ERROR 13:37:39,811 Failed to create /var/lib/cassandra/data/system/hints
directory
ERROR 13:37:39,811 Failed to create /var/lib/cassandra/data/system/hints
directory
ERROR 13:37:39,812 Failed to create
/var/lib/cassandra/data/system/schema_keyspaces directory
ERROR 13:37:39,812 Failed to create
/var/lib/cassandra/data/system/schema_keyspaces directory
ERROR 13:37:39,813 Failed to create
/var/lib/cassandra/data/system/schema_keyspaces directory
ERROR 13:37:39,814 Failed to create
/var/lib/cassandra/data/system/schema_keyspaces directory
ERROR 13:37:39,814 Failed to create
/var/lib/cassandra/data/system/schema_keyspaces directory
ERROR 13:37:39,815 Failed to create
/var/lib/cassandra/data/system/range_xfers directory
ERROR 13:37:39,816 Failed to create
/var/lib/cassandra/data/system/range_xfers directory
ERROR 13:37:39,817 Failed to create
/var/lib/cassandra/data/system/range_xfers directory
ERROR 13:37:39,817 Failed to create
/var/lib/cassandra/data/system/schema_columnfamilies directory
ERROR 13:37:39,818 Failed to create
/var/lib/cassandra/data/system/schema_columnfamilies directory
ERROR 13:37:39,818 Failed to create
/var/lib/cassandra/data/system/schema_columnfamilies directory
ERROR 13:37:39,820 Failed to create
[jira] [Updated] (CASSANDRA-5909) CommitLogReplayer date time issue
[
https://issues.apache.org/jira/browse/CASSANDRA-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-5909:
-
Attachment: 0001-CASSANDRA-5909.patch
Attached patch and test case as a fix to add precision. Thanks!
CommitLogReplayer date time issue
--
Key: CASSANDRA-5909
URL: https://issues.apache.org/jira/browse/CASSANDRA-5909
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Artur Kronenberg
Assignee: Vijay
Priority: Minor
Fix For: 1.2.10
Attachments: 0001-CASSANDRA-5909.patch
Hi,
First off I am sorry if the component is not right for this.
I am trying to get the point-in-time backup to work. And I ran into the
following issues:
1. The documentation in the commitlog_archiving.properties seems to be out of
date, as the example date format is no more valid and can't be parsed.
2.
The restore_point_in_time property seems to differ from the actual
maxTimeStamp. I added additional logging to the codebase in the class
CommitLogReplayer like that:
protected boolean pointInTimeExceeded(RowMutation frm)
{
long restoreTarget = CommitLog.instance.archiver.restorePointInTime;
logger.info(String.valueOf(restoreTarget));
for (ColumnFamily families : frm.getColumnFamilies())
{
logger.info(String.valueOf(families.maxTimestamp()));
if (families.maxTimestamp() restoreTarget)
return true;
}
return false;
}
The following output can be seen:
The restoreTarget timestamp is: 1377015783000
This has been correctly parsed as I added this date to the properties:
2013:08:20 17:23:03
the value for families.maxTimestamp() is: 1377009021033000
This date corresponds to: Mon 45605-09-05 10:50:33 BST (44 millennia from now)
It seems like the timestamp has 3 additional zeros. This also means that the
code can never return false on the call, as the restoreTarget will always be
smaller then the maxTimestamp(). Therefore the Replayer can never replay any
of my commitlog files.
The timestamp minus the 3 zeros corresponds to Tue 2013-08-20 15:30:21 BST
(23 hours ago) which makes more sense and would allow for the replay to
work.
My config:
Cassandra-1.2.4
Java 1.6
Ubuntu 12.04 64bit
If you need any more information let me know and I'll be happy to suply
whatever info I can.
-- artur
--
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
git commit: Fix QueryPagerTest
Updated Branches:
refs/heads/cassandra-2.0.0 f5c9b4a8b - c2847864c
Fix QueryPagerTest
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c2847864
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c2847864
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c2847864
Branch: refs/heads/cassandra-2.0.0
Commit: c2847864c6ec05320f18ba380104742b41ca4023
Parents: f5c9b4a
Author: Sylvain Lebresne sylv...@datastax.com
Authored: Tue Aug 27 10:50:07 2013 +0200
Committer: Sylvain Lebresne sylv...@datastax.com
Committed: Tue Aug 27 10:50:24 2013 +0200
--
test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c2847864/test/unit/org/apache/cassandra/service/QueryPagerTest.java
--
diff --git a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
index cf1a083..48893d4 100644
--- a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
+++ b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
@@ -119,7 +119,8 @@ public class QueryPagerTest extends SchemaLoader
private static ReadCommand sliceQuery(String key, String start, String
end, int count)
{
SliceQueryFilter filter = new SliceQueryFilter(bytes(start),
bytes(end), false, count);
-return new SliceFromReadCommand(KS, bytes(key), CF,
System.currentTimeMillis(), filter);
+// Note: for MultiQueryTest, we need the same timestamp/expireBefore
for all queries, so we just use 0 as it doesn't matter here.
+return new SliceFromReadCommand(KS, bytes(key), CF, 0, filter);
}
private static RangeSliceCommand
rangeNamesQuery(AbstractBoundsRowPosition range, int count, String... names)
[3/3] git commit: Merge branch 'cassandra-2.0' into trunk
Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/9e8391a4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/9e8391a4 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/9e8391a4 Branch: refs/heads/trunk Commit: 9e8391a481844fa277b01d64328cf0d14e779a6d Parents: 3bba76d e49261b Author: Sylvain Lebresne sylv...@datastax.com Authored: Tue Aug 27 10:51:00 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Tue Aug 27 10:51:00 2013 +0200 -- test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --
[1/2] git commit: Fix QueryPagerTest
Updated Branches:
refs/heads/cassandra-2.0 db381eaa0 - e49261b46
Fix QueryPagerTest
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c2847864
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c2847864
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c2847864
Branch: refs/heads/cassandra-2.0
Commit: c2847864c6ec05320f18ba380104742b41ca4023
Parents: f5c9b4a
Author: Sylvain Lebresne sylv...@datastax.com
Authored: Tue Aug 27 10:50:07 2013 +0200
Committer: Sylvain Lebresne sylv...@datastax.com
Committed: Tue Aug 27 10:50:24 2013 +0200
--
test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c2847864/test/unit/org/apache/cassandra/service/QueryPagerTest.java
--
diff --git a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
index cf1a083..48893d4 100644
--- a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
+++ b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
@@ -119,7 +119,8 @@ public class QueryPagerTest extends SchemaLoader
private static ReadCommand sliceQuery(String key, String start, String
end, int count)
{
SliceQueryFilter filter = new SliceQueryFilter(bytes(start),
bytes(end), false, count);
-return new SliceFromReadCommand(KS, bytes(key), CF,
System.currentTimeMillis(), filter);
+// Note: for MultiQueryTest, we need the same timestamp/expireBefore
for all queries, so we just use 0 as it doesn't matter here.
+return new SliceFromReadCommand(KS, bytes(key), CF, 0, filter);
}
private static RangeSliceCommand
rangeNamesQuery(AbstractBoundsRowPosition range, int count, String... names)
[2/3] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e49261b4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e49261b4 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e49261b4 Branch: refs/heads/trunk Commit: e49261b46f8db7ccee4205b6dc54741e5d2cc73e Parents: db381ea c284786 Author: Sylvain Lebresne sylv...@datastax.com Authored: Tue Aug 27 10:50:45 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Tue Aug 27 10:50:45 2013 +0200 -- test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --
[1/3] git commit: Fix QueryPagerTest
Updated Branches:
refs/heads/trunk 3bba76dd1 - 9e8391a48
Fix QueryPagerTest
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c2847864
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c2847864
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c2847864
Branch: refs/heads/trunk
Commit: c2847864c6ec05320f18ba380104742b41ca4023
Parents: f5c9b4a
Author: Sylvain Lebresne sylv...@datastax.com
Authored: Tue Aug 27 10:50:07 2013 +0200
Committer: Sylvain Lebresne sylv...@datastax.com
Committed: Tue Aug 27 10:50:24 2013 +0200
--
test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c2847864/test/unit/org/apache/cassandra/service/QueryPagerTest.java
--
diff --git a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
index cf1a083..48893d4 100644
--- a/test/unit/org/apache/cassandra/service/QueryPagerTest.java
+++ b/test/unit/org/apache/cassandra/service/QueryPagerTest.java
@@ -119,7 +119,8 @@ public class QueryPagerTest extends SchemaLoader
private static ReadCommand sliceQuery(String key, String start, String
end, int count)
{
SliceQueryFilter filter = new SliceQueryFilter(bytes(start),
bytes(end), false, count);
-return new SliceFromReadCommand(KS, bytes(key), CF,
System.currentTimeMillis(), filter);
+// Note: for MultiQueryTest, we need the same timestamp/expireBefore
for all queries, so we just use 0 as it doesn't matter here.
+return new SliceFromReadCommand(KS, bytes(key), CF, 0, filter);
}
private static RangeSliceCommand
rangeNamesQuery(AbstractBoundsRowPosition range, int count, String... names)
[2/2] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e49261b4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e49261b4 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e49261b4 Branch: refs/heads/cassandra-2.0 Commit: e49261b46f8db7ccee4205b6dc54741e5d2cc73e Parents: db381ea c284786 Author: Sylvain Lebresne sylv...@datastax.com Authored: Tue Aug 27 10:50:45 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Tue Aug 27 10:50:45 2013 +0200 -- test/unit/org/apache/cassandra/service/QueryPagerTest.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --
[1/6] git commit: Add stream session progress to JMX
Updated Branches:
refs/heads/cassandra-2.0 e49261b46 - 1bc2fc597
refs/heads/cassandra-2.0.0 c2847864c - cf1de3112
refs/heads/trunk 9e8391a48 - 748beafeb
Add stream session progress to JMX
patch by Greg DeAngelis; reviewed by yukim for CASSANDRA-4757
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cf1de311
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cf1de311
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/cf1de311
Branch: refs/heads/cassandra-2.0
Commit: cf1de311224dce9c3db51db9dcbeae30bb22cfd0
Parents: c284786
Author: Greg DeAngelis gdean...@gmail.com
Authored: Mon Aug 26 15:22:55 2013 -0500
Committer: Yuki Morishita yu...@apache.org
Committed: Tue Aug 27 07:36:29 2013 -0500
--
CHANGES.txt | 1 +
.../management/StreamStateCompositeData.java| 38 ++--
2 files changed, 36 insertions(+), 3 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index cfc4845..b910f14 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,6 +3,7 @@
* Fix periodic memtable flushing behavior with clean memtables
(CASSANDRA-5931)
* Fix dateOf() function for pre-2.0 timestamp columns (CASSANDRA-5928)
* Fix SSTable unintentionally loads BF when opened for batch (CASSANDRA-5938)
+ * Add stream session progress to JMX (CASSANDRA-4757)
Merged from 1.2:
* Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* Don't announce schema version until we've loaded the changes locally
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
--
diff --git
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
index 820a71a..3752d39 100644
---
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
+++
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
@@ -33,10 +33,18 @@ import org.apache.cassandra.streaming.StreamState;
*/
public class StreamStateCompositeData
{
-private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions};
+private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions,
+currentRxBytes,
totalRxBytes, rxPercentage,
+currentTxBytes,
totalTxBytes, txPercentage};
private static final String[] ITEM_DESCS = new String[]{Plan ID of this
stream,
Stream plan
description,
-Active stream
sessions};
+Active stream
sessions,
+Number of bytes
received across all streams,
+Total bytes
available to receive across all streams,
+Percentage
received across all streams,
+Number of bytes
sent across all streams,
+Total bytes
available to send across all streams,
+Percentage sent
across all streams};
private static final OpenType?[] ITEM_TYPES;
public static final CompositeType COMPOSITE_TYPE;
@@ -45,7 +53,9 @@ public class StreamStateCompositeData
{
ITEM_TYPES = new OpenType[]{SimpleType.STRING,
SimpleType.STRING,
-
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE)};
+
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE),
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE,
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE};
COMPOSITE_TYPE = new CompositeType(StreamState.class.getName(),
StreamState,
ITEM_NAMES,
@@ -73,6 +83,28 @@ public class StreamStateCompositeData
}
})).toArray(sessions);
valueMap.put(ITEM_NAMES[2],
[2/6] git commit: Add stream session progress to JMX
Add stream session progress to JMX
patch by Greg DeAngelis; reviewed by yukim for CASSANDRA-4757
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cf1de311
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cf1de311
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/cf1de311
Branch: refs/heads/cassandra-2.0.0
Commit: cf1de311224dce9c3db51db9dcbeae30bb22cfd0
Parents: c284786
Author: Greg DeAngelis gdean...@gmail.com
Authored: Mon Aug 26 15:22:55 2013 -0500
Committer: Yuki Morishita yu...@apache.org
Committed: Tue Aug 27 07:36:29 2013 -0500
--
CHANGES.txt | 1 +
.../management/StreamStateCompositeData.java| 38 ++--
2 files changed, 36 insertions(+), 3 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index cfc4845..b910f14 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,6 +3,7 @@
* Fix periodic memtable flushing behavior with clean memtables
(CASSANDRA-5931)
* Fix dateOf() function for pre-2.0 timestamp columns (CASSANDRA-5928)
* Fix SSTable unintentionally loads BF when opened for batch (CASSANDRA-5938)
+ * Add stream session progress to JMX (CASSANDRA-4757)
Merged from 1.2:
* Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* Don't announce schema version until we've loaded the changes locally
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
--
diff --git
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
index 820a71a..3752d39 100644
---
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
+++
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
@@ -33,10 +33,18 @@ import org.apache.cassandra.streaming.StreamState;
*/
public class StreamStateCompositeData
{
-private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions};
+private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions,
+currentRxBytes,
totalRxBytes, rxPercentage,
+currentTxBytes,
totalTxBytes, txPercentage};
private static final String[] ITEM_DESCS = new String[]{Plan ID of this
stream,
Stream plan
description,
-Active stream
sessions};
+Active stream
sessions,
+Number of bytes
received across all streams,
+Total bytes
available to receive across all streams,
+Percentage
received across all streams,
+Number of bytes
sent across all streams,
+Total bytes
available to send across all streams,
+Percentage sent
across all streams};
private static final OpenType?[] ITEM_TYPES;
public static final CompositeType COMPOSITE_TYPE;
@@ -45,7 +53,9 @@ public class StreamStateCompositeData
{
ITEM_TYPES = new OpenType[]{SimpleType.STRING,
SimpleType.STRING,
-
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE)};
+
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE),
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE,
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE};
COMPOSITE_TYPE = new CompositeType(StreamState.class.getName(),
StreamState,
ITEM_NAMES,
@@ -73,6 +83,28 @@ public class StreamStateCompositeData
}
})).toArray(sessions);
valueMap.put(ITEM_NAMES[2], sessions);
+
+long currentRxBytes = 0;
+long totalRxBytes = 0;
+long currentTxBytes = 0;
+long totalTxBytes = 0;
+for
[5/6] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1bc2fc59 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1bc2fc59 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1bc2fc59 Branch: refs/heads/cassandra-2.0 Commit: 1bc2fc59725b96b7a5e57d30cd4520e20e80bc74 Parents: e49261b cf1de31 Author: Yuki Morishita yu...@apache.org Authored: Tue Aug 27 07:36:38 2013 -0500 Committer: Yuki Morishita yu...@apache.org Committed: Tue Aug 27 07:36:38 2013 -0500 -- CHANGES.txt | 1 + .../management/StreamStateCompositeData.java| 38 ++-- 2 files changed, 36 insertions(+), 3 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1bc2fc59/CHANGES.txt --
[4/6] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1bc2fc59 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1bc2fc59 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1bc2fc59 Branch: refs/heads/trunk Commit: 1bc2fc59725b96b7a5e57d30cd4520e20e80bc74 Parents: e49261b cf1de31 Author: Yuki Morishita yu...@apache.org Authored: Tue Aug 27 07:36:38 2013 -0500 Committer: Yuki Morishita yu...@apache.org Committed: Tue Aug 27 07:36:38 2013 -0500 -- CHANGES.txt | 1 + .../management/StreamStateCompositeData.java| 38 ++-- 2 files changed, 36 insertions(+), 3 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1bc2fc59/CHANGES.txt --
[6/6] git commit: Merge branch 'cassandra-2.0' into trunk
Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/748beafe Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/748beafe Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/748beafe Branch: refs/heads/trunk Commit: 748beafeba22355501648dc87e5c525d6ec1ba22 Parents: 9e8391a 1bc2fc5 Author: Yuki Morishita yu...@apache.org Authored: Tue Aug 27 07:36:51 2013 -0500 Committer: Yuki Morishita yu...@apache.org Committed: Tue Aug 27 07:36:51 2013 -0500 -- CHANGES.txt | 1 + .../management/StreamStateCompositeData.java| 38 ++-- 2 files changed, 36 insertions(+), 3 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/748beafe/CHANGES.txt --
[3/6] git commit: Add stream session progress to JMX
Add stream session progress to JMX
patch by Greg DeAngelis; reviewed by yukim for CASSANDRA-4757
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cf1de311
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cf1de311
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/cf1de311
Branch: refs/heads/trunk
Commit: cf1de311224dce9c3db51db9dcbeae30bb22cfd0
Parents: c284786
Author: Greg DeAngelis gdean...@gmail.com
Authored: Mon Aug 26 15:22:55 2013 -0500
Committer: Yuki Morishita yu...@apache.org
Committed: Tue Aug 27 07:36:29 2013 -0500
--
CHANGES.txt | 1 +
.../management/StreamStateCompositeData.java| 38 ++--
2 files changed, 36 insertions(+), 3 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index cfc4845..b910f14 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,6 +3,7 @@
* Fix periodic memtable flushing behavior with clean memtables
(CASSANDRA-5931)
* Fix dateOf() function for pre-2.0 timestamp columns (CASSANDRA-5928)
* Fix SSTable unintentionally loads BF when opened for batch (CASSANDRA-5938)
+ * Add stream session progress to JMX (CASSANDRA-4757)
Merged from 1.2:
* Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* Don't announce schema version until we've loaded the changes locally
http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf1de311/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
--
diff --git
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
index 820a71a..3752d39 100644
---
a/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
+++
b/src/java/org/apache/cassandra/streaming/management/StreamStateCompositeData.java
@@ -33,10 +33,18 @@ import org.apache.cassandra.streaming.StreamState;
*/
public class StreamStateCompositeData
{
-private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions};
+private static final String[] ITEM_NAMES = new String[]{planId,
description, sessions,
+currentRxBytes,
totalRxBytes, rxPercentage,
+currentTxBytes,
totalTxBytes, txPercentage};
private static final String[] ITEM_DESCS = new String[]{Plan ID of this
stream,
Stream plan
description,
-Active stream
sessions};
+Active stream
sessions,
+Number of bytes
received across all streams,
+Total bytes
available to receive across all streams,
+Percentage
received across all streams,
+Number of bytes
sent across all streams,
+Total bytes
available to send across all streams,
+Percentage sent
across all streams};
private static final OpenType?[] ITEM_TYPES;
public static final CompositeType COMPOSITE_TYPE;
@@ -45,7 +53,9 @@ public class StreamStateCompositeData
{
ITEM_TYPES = new OpenType[]{SimpleType.STRING,
SimpleType.STRING,
-
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE)};
+
ArrayType.getArrayType(SessionInfoCompositeData.COMPOSITE_TYPE),
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE,
+ SimpleType.LONG, SimpleType.LONG,
SimpleType.DOUBLE};
COMPOSITE_TYPE = new CompositeType(StreamState.class.getName(),
StreamState,
ITEM_NAMES,
@@ -73,6 +83,28 @@ public class StreamStateCompositeData
}
})).toArray(sessions);
valueMap.put(ITEM_NAMES[2], sessions);
+
+long currentRxBytes = 0;
+long totalRxBytes = 0;
+long currentTxBytes = 0;
+long totalTxBytes = 0;
+for
[jira] [Updated] (CASSANDRA-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5925:
Attachment: (was: 0001-Write-ballot-with-proposal.txt)
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0.1
Attachments: TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5925:
Attachment: 5925.txt
Thanks for the test.
There is indeed 2 problems:
# the NPE while loading the paxos state. Contrarily to my first reading, the
fact that savePaxosProposal doesn't save the inProgress ballot is not only a
problem due to expiration. We may call that method if our own inProgress is
older than the proposal, so given a node received a proposal without having
seen the prepare first (and without having a previous state), we'd end up with
a state where just the 'proposal' column is set. Note that technically, I don't
think it breaks Paxos not to update the ballot when saving a proposal so we
could just fix loadPaxosState to not NPE in that case, but it feels
saner/simpler to me to write the proposal ballot when we save a proposal value.
# the reason Phil test fails is different however. The problem is that when we
were building the 'expected' ColumnFamily for the cas() call in CQL3, we were
using the full parameters of the statement, including (which was the problem)
the TTL. In that test, the TTL is 1 second, so it's possible (and even not that
unlikely since we only have up to 1 second accuracy internally) that when we
were comparing 'expected' to 'current' the expected column was considered
deleted. So, if when the 2nd update to a row was processed the first one had
expired (again, not unlikely given the 1 second ttl), the 2nd CAS update was
comparing both a deleted 'expected' and a deleted 'current', thus succeeding.
So anyway, the fix is to not use the TTL for the conditions in
ModificationStatement.
So attaching patch that fix both issue.
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0.1
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
[jira] [Created] (CASSANDRA-5940) Create a ppa to make Debian/Ubuntu installation easier
Andrew Pennebaker created CASSANDRA-5940: Summary: Create a ppa to make Debian/Ubuntu installation easier Key: CASSANDRA-5940 URL: https://issues.apache.org/jira/browse/CASSANDRA-5940 Project: Cassandra Issue Type: Improvement Environment: Debian/Ubuntu Reporter: Andrew Pennebaker Priority: Minor We could simplify the installation process for Debian/Ubuntu users by offering a ppa, turning a five step process into a three step process. The DebianPackaging wiki article is a good start for this. https://wiki.apache.org/cassandra/DebianPackaging -- 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-5941) Incorrect Schema with PIG CqlStorage Queries
James Schappet created CASSANDRA-5941:
-
Summary: Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be cast
to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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] [Assigned] (CASSANDRA-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-5941:
---
Assignee: Alex Liu
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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] [Resolved] (CASSANDRA-5828) add counters coverage to upgrade tests
[ https://issues.apache.org/jira/browse/CASSANDRA-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Meyer resolved CASSANDRA-5828. - Resolution: Fixed add counters coverage to upgrade tests -- Key: CASSANDRA-5828 URL: https://issues.apache.org/jira/browse/CASSANDRA-5828 Project: Cassandra Issue Type: Test Components: Tests Reporter: Cathy Daw Assignee: Daniel Meyer Fix For: 1.2.9, 2.0.1 this was encountered as missing coverage when upgrading to 1.2.7 -- 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-5828) add counters coverage to upgrade tests
[ https://issues.apache.org/jira/browse/CASSANDRA-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751389#comment-13751389 ] Daniel Meyer commented on CASSANDRA-5828: - https://github.com/riptano/cassandra-dtest/commit/24b5295ce95b4984a71714d76acc5480bf3b6dbb#upgrade_through_versions_test.py add counters coverage to upgrade tests -- Key: CASSANDRA-5828 URL: https://issues.apache.org/jira/browse/CASSANDRA-5828 Project: Cassandra Issue Type: Test Components: Tests Reporter: Cathy Daw Assignee: Daniel Meyer Fix For: 1.2.9, 2.0.1 this was encountered as missing coverage when upgrading to 1.2.7 -- 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-5942) bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values
[ https://issues.apache.org/jira/browse/CASSANDRA-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Meyer updated CASSANDRA-5942: Attachment: logs.tar upgrade_through_versions_test.py bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values --- Key: CASSANDRA-5942 URL: https://issues.apache.org/jira/browse/CASSANDRA-5942 Project: Cassandra Issue Type: Bug Environment: java version 1.7.0_25 Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) Reporter: Daniel Meyer Fix For: 2.0 Attachments: logs.tar, upgrade_through_versions_test.py Running the latest version of upgrade_through_versions_test will randomly fail at a rate of about 1 out of 5 runs due to an incorrect counter value. A slightly modified version of the test is attached for reference. This version has trunk eliminated from the versions list and an extra debugging statement. The problem occurs after upgrading to the 2.0 branch from the 1.2 branch and after boostrapping a new node to the cluster. Best way to repro is just run the test in a loop 5 to 10 times. Be sure to set PRINT_DEBUG env variable to true and run test with --nocapture to see the debug output. Logs are also included. -- 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-5942) bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values
Daniel Meyer created CASSANDRA-5942: --- Summary: bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values Key: CASSANDRA-5942 URL: https://issues.apache.org/jira/browse/CASSANDRA-5942 Project: Cassandra Issue Type: Bug Environment: java version 1.7.0_25 Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) Reporter: Daniel Meyer Fix For: 2.0 Attachments: logs.tar, upgrade_through_versions_test.py Running the latest version of upgrade_through_versions_test will randomly fail at a rate of about 1 out of 5 runs due to an incorrect counter value. A slightly modified version of the test is attached for reference. This version has trunk eliminated from the versions list and an extra debugging statement. The problem occurs after upgrading to the 2.0 branch from the 1.2 branch and after boostrapping a new node to the cluster. Best way to repro is just run the test in a loop 5 to 10 times. Be sure to set PRINT_DEBUG env variable to true and run test with --nocapture to see the debug output. Logs are also included. -- 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-4206) AssertionError: originally calculated column size of 629444349 but now it is 588008950
[
https://issues.apache.org/jira/browse/CASSANDRA-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751424#comment-13751424
]
Nate McCall commented on CASSANDRA-4206:
FTR - seeing this currently in 1.2.8 on batchlog compaction attempt
(unfortunately I can't easily modify the gc_grace for this). Stack trace:
{code}
ERROR [CompactionExecutor:105] 2013-08-27 17:54:39,942 CassandraDaemon.java
(line 192) Exception in thread Thread[CompactionExecutor:105,1,main]
java.lang.AssertionError: originally calculated column size of 17391408 but now
it is 17391426
at
org.apache.cassandra.db.compaction.LazilyCompactedRow.write(LazilyCompactedRow.java:135)
at
org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:160)
at
org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:162)
at
org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
at
org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
at
org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
at
org.apache.cassandra.db.compaction.CompactionManager$7.runMayThrow(CompactionManager.java:445)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
ERROR [OptionalTasks:1] 2013-08-27 17:54:39,942 CassandraDaemon.java (line 192)
Exception in thread Thread[OptionalTasks:1,5,main]
{code}
AssertionError: originally calculated column size of 629444349 but now it is
588008950
--
Key: CASSANDRA-4206
URL: https://issues.apache.org/jira/browse/CASSANDRA-4206
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.9
Environment: Debian Squeeze Linux, kernel 2.6.32, sun-java6-bin
6.26-0squeeze1
Reporter: Patrik Modesto
I've 4 node cluster of Cassandra 1.0.9. There is a rfTest3 keyspace with RF=3
and one CF with two secondary indexes. I'm importing data into this CF using
Hadoop Mapreduce job, each row has less than 10 colkumns. From JMX:
MaxRowSize: 1597
MeanRowSize: 369
And there are some tens of millions of rows.
It's write-heavy usage and there is a big pressure on each node, there are
quite some dropped mutations on each node. After ~12 hours of inserting I see
these assertion exceptiona on 3 out of four nodes:
{noformat}
ERROR 06:25:40,124 Fatal exception in thread Thread[HintedHandoff:1,1,main]
java.lang.RuntimeException: java.util.concurrent.ExecutionException:
java.lang.AssertionError: originally calculated column size of 629444349 but
now it is 588008950
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpointInternal(HintedHandOffManager.java:388)
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpoint(HintedHandOffManager.java:256)
at
org.apache.cassandra.db.HintedHandOffManager.access$300(HintedHandOffManager.java:84)
at
org.apache.cassandra.db.HintedHandOffManager$3.runMayThrow(HintedHandOffManager.java:437)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
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)
Caused by: java.util.concurrent.ExecutionException:
java.lang.AssertionError: originally calculated column size of
629444349 but now it is 588008950
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpointInternal(HintedHandOffManager.java:384)
... 7 more
Caused by: java.lang.AssertionError: originally calculated column size
of 629444349 but now it is 588008950
at
org.apache.cassandra.db.compaction.LazilyCompactedRow.write(LazilyCompactedRow.java:124)
at
org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:160)
at
[jira] [Commented] (CASSANDRA-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751441#comment-13751441
]
Alex Liu commented on CASSANDRA-5941:
-
[~schappetj]Can you try patch 5867-bug-fix-filter-push-down-1.2-branch.txt on
CASSANDRA-5876?
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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] [Comment Edited] (CASSANDRA-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751441#comment-13751441
]
Alex Liu edited comment on CASSANDRA-5941 at 8/27/13 5:00 PM:
--
[~schappetj]Can you try patch 5867-bug-fix-filter-push-down-1.2-branch.txt on
CASSANDRA-5867?
was (Author: alexliu68):
[~schappetj]Can you try patch 5867-bug-fix-filter-push-down-1.2-branch.txt
on CASSANDRA-5876?
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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-4206) AssertionError: originally calculated column size of 629444349 but now it is 588008950
[
https://issues.apache.org/jira/browse/CASSANDRA-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751463#comment-13751463
]
Jonathan Ellis commented on CASSANDRA-4206:
---
TBH I'm not sure we're going to fix this in 1.2.x. If you have a snapshot set
of sstables that can reproduce it, then we can dig in, but eyeballing the code
hasn't fixed it yet (despite multiple efforts) and probably won't.
The good news is that 2.0 fixed it by always doing single-pass compaction.
AssertionError: originally calculated column size of 629444349 but now it is
588008950
--
Key: CASSANDRA-4206
URL: https://issues.apache.org/jira/browse/CASSANDRA-4206
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.9
Environment: Debian Squeeze Linux, kernel 2.6.32, sun-java6-bin
6.26-0squeeze1
Reporter: Patrik Modesto
I've 4 node cluster of Cassandra 1.0.9. There is a rfTest3 keyspace with RF=3
and one CF with two secondary indexes. I'm importing data into this CF using
Hadoop Mapreduce job, each row has less than 10 colkumns. From JMX:
MaxRowSize: 1597
MeanRowSize: 369
And there are some tens of millions of rows.
It's write-heavy usage and there is a big pressure on each node, there are
quite some dropped mutations on each node. After ~12 hours of inserting I see
these assertion exceptiona on 3 out of four nodes:
{noformat}
ERROR 06:25:40,124 Fatal exception in thread Thread[HintedHandoff:1,1,main]
java.lang.RuntimeException: java.util.concurrent.ExecutionException:
java.lang.AssertionError: originally calculated column size of 629444349 but
now it is 588008950
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpointInternal(HintedHandOffManager.java:388)
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpoint(HintedHandOffManager.java:256)
at
org.apache.cassandra.db.HintedHandOffManager.access$300(HintedHandOffManager.java:84)
at
org.apache.cassandra.db.HintedHandOffManager$3.runMayThrow(HintedHandOffManager.java:437)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
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)
Caused by: java.util.concurrent.ExecutionException:
java.lang.AssertionError: originally calculated column size of
629444349 but now it is 588008950
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpointInternal(HintedHandOffManager.java:384)
... 7 more
Caused by: java.lang.AssertionError: originally calculated column size
of 629444349 but now it is 588008950
at
org.apache.cassandra.db.compaction.LazilyCompactedRow.write(LazilyCompactedRow.java:124)
at
org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:160)
at
org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:161)
at
org.apache.cassandra.db.compaction.CompactionManager$7.call(CompactionManager.java:380)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
{noformat}
Few lines regarding Hints from the output.log:
{noformat}
INFO 06:21:26,202 Compacting large row
system/HintsColumnFamily:7000 (1712834057 bytes)
incrementally
INFO 06:22:52,610 Compacting large row
system/HintsColumnFamily:1000 (2616073981 bytes)
incrementally
INFO 06:22:59,111 flushing high-traffic column family CFS(Keyspace='system',
ColumnFamily='HintsColumnFamily') (estimated 305147360 bytes)
INFO 06:22:59,813 Enqueuing flush of
Memtable-HintsColumnFamily@833933926(3814342/305147360 serialized/live bytes,
7452 ops)
INFO 06:22:59,814 Writing
Memtable-HintsColumnFamily@833933926(3814342/305147360 serialized/live bytes,
7452 ops)
{noformat}
I think the problem may be somehow connected to an IntegerType secondary
index. I had a different problem with CF with two secondary indexes, the
first UTF8Type, the second IntegerType. After a few hours of inserting data
in the afternoon and midnight repair+compact, the next day I couldn't find
any row using the IntegerType secondary index. The output was like this:
{noformat}
[default@rfTest3] get IndexTest where col1 =
'3230727:http://zaskolak.cz/download.php';
[jira] [Commented] (CASSANDRA-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751535#comment-13751535
]
James Schappet commented on CASSANDRA-5941:
---
Please pardon my ignorance, but I have never applied a patch.
How do I apply it? and to what version should it be applied?
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751546#comment-13751546
]
Alex Liu commented on CASSANDRA-5941:
-
git checkout cassandra-1.2 branch. then patch -p1
5867-bug-fix-filter-push-down-1.2-branch.txt
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751553#comment-13751553
]
Phil Persad commented on CASSANDRA-5925:
I applied the patch and it does seem to improve the situation. Unfortunately,
I'm still seeing double consumptions. However, the occurrence has dropped from
1-2% to 0.002%-0.04%. That rate is low enough that it may not show up with the
sample size of 40,000 in the test I posted. Increasing the iterations by 10-20
times should serve to demonstrate the issue.
For the sake of exploration, after I patched I tried running the test both with
and without the TTL in the update statement an saw no appreciable difference in
the number of failures. It looks like there may be yet a third problem.
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751555#comment-13751555
]
Jonathan Ellis commented on CASSANDRA-5925:
---
+1
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5941) Incorrect Schema with PIG CqlStorage Queries
[
https://issues.apache.org/jira/browse/CASSANDRA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751561#comment-13751561
]
James Schappet commented on CASSANDRA-5941:
---
That fixed it. It's now filtering as expected.
Incorrect Schema with PIG CqlStorage Queries
Key: CASSANDRA-5941
URL: https://issues.apache.org/jira/browse/CASSANDRA-5941
Project: Cassandra
Issue Type: Bug
Reporter: James Schappet
Assignee: Alex Liu
A = LOAD 'cql://my/data?where_clause=key%3D\'status\' ' USING CqlStorage() AS
(
type:chararray,
barcode:chararray,
row_id:bytearray,
key:chararray,
status:chararray
);
DESCRIBE A;
--A: {type: chararray,barcode: chararray,row_id: bytearray,key:
chararray,status: chararray}
B = FOREACH A GENERATE FLATTEN( status );
I am trying to process the following data:
B = FOREACH A GENERATE FLATTEN( status);
DUMB B;
(value,LIVING)
(value,LIVING)
(value,LIVING)
(value,DECEASED)
(value,LIVING)
(value,DECEASED)
(value,DECEASED)
(value,LIVING)
But when I try to filter it (FILTER A BY status MATCHES 'DECEASED')
I get the following error:
2013-08-23 08:47:16,290 [Thread-4] WARN
org.apache.hadoop.mapred.LocalJobRunner - job_local_0001
java.lang.ClassCastException: org.apache.pig.data.BinSedesTuple cannot be
cast to java.lang.String
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.getNext(PORegexp.java:84)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNext(POFilter.java:148)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:290)
at
org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.getNext(POForEach.java:233)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigGenericMapReduce$Reduce.runPipeline(PigGenericMapReduce.java:460)
...
There are two StackOverFlow questions related to this:
http://stackoverflow.com/questions/18407248/cce-binsedestuple-cannot-be-cast-to-string?lq=1
http://stackoverflow.com/questions/18391552/cqlstorage-generates-wrong-pig-schema?lq=1
--
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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751565#comment-13751565
]
Sylvain Lebresne commented on CASSANDRA-5925:
-
bq. I applied the patch and it does seem to improve the situation.
Unfortunately, I'm still seeing double consumptions. However, the occurrence
has dropped from 1-2% to 0.002%-0.04%
Forgot to say, your test is actually broken in theory because it picks random
keys. It is thus possible for an insert of one of the jobs to interleave with
the updates of another one, thus making both update apply (and presumably both
update of the other job fail, but the test don't check for that). So I'd
suggest first re-running with guaranteed unique keys. If it still fails, I'm
happy to look at it more deeply, though we did fixed 2 problem so let's commit
those and open a separate ticket if a 3rd problem there is indeed (and if there
is 3rd that take more than 40K iterations to manifest itself, chances are it
will be tricky to track down, so it's not worth holding on the initial fixes).
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5943) Add sstablesplit dtest
Brandon Williams created CASSANDRA-5943: --- Summary: Add sstablesplit dtest Key: CASSANDRA-5943 URL: https://issues.apache.org/jira/browse/CASSANDRA-5943 Project: Cassandra Issue Type: Test Reporter: Brandon Williams Assignee: Daniel Meyer Priority: Minor Now that we're shipping sstablesplit, we should add a dtest to make sure it works correctly. -- 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-5838) Upgrade metrics-core library
[ https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751612#comment-13751612 ] Chris Burroughs commented on CASSANDRA-5838: Not sure if this ticket is the right place, but could we upgrade to the latest metrics v2 in cassandra 2.0.x? Upgrade metrics-core library Key: CASSANDRA-5838 URL: https://issues.apache.org/jira/browse/CASSANDRA-5838 Project: Cassandra Issue Type: Improvement Reporter: Eugen Paraschiv Assignee: Dave Brosius Priority: Minor Fix For: 2.1 Attachments: 5838-2.txt, 5838-3.txt, 5838.txt Cassandra is now using [metrics|https://github.com/codahale/metrics] and is depending on metrics-core 2.0.3. It would be great to make the jump to the latest version of the library which is 3.x - [latest is 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22]. -- 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-5838) Upgrade metrics-core library
[ https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751631#comment-13751631 ] Jonathan Ellis commented on CASSANDRA-5838: --- What problems does that solve? Upgrade metrics-core library Key: CASSANDRA-5838 URL: https://issues.apache.org/jira/browse/CASSANDRA-5838 Project: Cassandra Issue Type: Improvement Reporter: Eugen Paraschiv Assignee: Dave Brosius Priority: Minor Fix For: 2.1 Attachments: 5838-2.txt, 5838-3.txt, 5838.txt Cassandra is now using [metrics|https://github.com/codahale/metrics] and is depending on metrics-core 2.0.3. It would be great to make the jump to the latest version of the library which is 3.x - [latest is 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22]. -- 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-5838) Upgrade metrics-core library
[ https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751635#comment-13751635 ] Michael Rose commented on CASSANDRA-5838: - It would be advantageous to wait for Metrics 3.1. https://groups.google.com/forum/#!topic/metrics-user/Mr3H7rXOvtA According to Coda, 3.1 will include the ability to provide a custom naming strategy to the JMXReporter. Otherwise every monitoring tool built around JMX will break. Upgrade metrics-core library Key: CASSANDRA-5838 URL: https://issues.apache.org/jira/browse/CASSANDRA-5838 Project: Cassandra Issue Type: Improvement Reporter: Eugen Paraschiv Assignee: Dave Brosius Priority: Minor Fix For: 2.1 Attachments: 5838-2.txt, 5838-3.txt, 5838.txt Cassandra is now using [metrics|https://github.com/codahale/metrics] and is depending on metrics-core 2.0.3. It would be great to make the jump to the latest version of the library which is 3.x - [latest is 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22]. -- 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-5838) Upgrade metrics-core library
[ https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751650#comment-13751650 ] Nick Bailey commented on CASSANDRA-5838: So this changes moves all the mbeans into a single domain due to how 3.0 does things (see attached picture). This will break all existing clients for the new metrics mbeans (did we update nodetool and such or are they using the old mbeans?). I'm not really a huge fan of this change for that reason. From discussion on IRC it looks like we'd need to have multiple jmx reporters defined to match the old behavior. Or there is some speculation that this might be fixed/easier in metrics 3.1. I'd be in favor of reverting this until we can figure out how to match the old format or confirm the current behavior (breaking) is absolutely what we want going forward. Upgrade metrics-core library Key: CASSANDRA-5838 URL: https://issues.apache.org/jira/browse/CASSANDRA-5838 Project: Cassandra Issue Type: Improvement Reporter: Eugen Paraschiv Assignee: Dave Brosius Priority: Minor Fix For: 2.1 Attachments: 5838-2.txt, 5838-3.txt, 5838.txt, Screen Shot 2013-08-27 at 2.53.39 PM.png Cassandra is now using [metrics|https://github.com/codahale/metrics] and is depending on metrics-core 2.0.3. It would be great to make the jump to the latest version of the library which is 3.x - [latest is 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22]. -- 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-5838) Upgrade metrics-core library
[ https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Bailey updated CASSANDRA-5838: --- Attachment: Screen Shot 2013-08-27 at 2.53.39 PM.png Upgrade metrics-core library Key: CASSANDRA-5838 URL: https://issues.apache.org/jira/browse/CASSANDRA-5838 Project: Cassandra Issue Type: Improvement Reporter: Eugen Paraschiv Assignee: Dave Brosius Priority: Minor Fix For: 2.1 Attachments: 5838-2.txt, 5838-3.txt, 5838.txt, Screen Shot 2013-08-27 at 2.53.39 PM.png Cassandra is now using [metrics|https://github.com/codahale/metrics] and is depending on metrics-core 2.0.3. It would be great to make the jump to the latest version of the library which is 3.x - [latest is 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22]. -- 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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751653#comment-13751653
]
Phil Persad commented on CASSANDRA-5925:
I take your point and I'll tweak my test to check for duplicate keys. That
being said, even without the use of SecureRandom, I seriously doubt that I'm
getting collisions on a 64 Byte key.
I'll create a new ticket once I've had time to update my test.
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5944) Stress latency for 99.9th percentile is mislabed as 99th.
Ryan McGuire created CASSANDRA-5944:
---
Summary: Stress latency for 99.9th percentile is mislabed as 99th.
Key: CASSANDRA-5944
URL: https://issues.apache.org/jira/browse/CASSANDRA-5944
Project: Cassandra
Issue Type: Bug
Reporter: Ryan McGuire
Priority: Trivial
The specific call in stress is calling latency.get999thPercentile() - so it
would be less confusing if the first line of stress output were this:
{code}
total,interval_op_rate,interval_key_rate,latency,95th,99.9th,elapsed_time
{code}
Listing 99.9th instead of 99th.
--
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-5288) stress percentile label does not match what is returned
[ https://issues.apache.org/jira/browse/CASSANDRA-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751659#comment-13751659 ] Ryan McGuire commented on CASSANDRA-5288: - As far as I know, it's actually reporting 99.9th percentile, so I agree, the heading is mislabled. stress percentile label does not match what is returned --- Key: CASSANDRA-5288 URL: https://issues.apache.org/jira/browse/CASSANDRA-5288 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 1.2.2 Reporter: Chris Burroughs Assignee: Brandon Williams Priority: Minor We say it's the 99th: https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L65 But return 99.9th https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L145 Not sure which is intended. -- 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] [Resolved] (CASSANDRA-5944) Stress latency for 99.9th percentile is mislabed as 99th.
[
https://issues.apache.org/jira/browse/CASSANDRA-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McGuire resolved CASSANDRA-5944.
-
Resolution: Duplicate
Reproduced In: 2.0 rc2, 1.2.10 (was: 1.2.10, 2.0 rc2)
Stress latency for 99.9th percentile is mislabed as 99th.
-
Key: CASSANDRA-5944
URL: https://issues.apache.org/jira/browse/CASSANDRA-5944
Project: Cassandra
Issue Type: Bug
Reporter: Ryan McGuire
Priority: Trivial
The specific call in stress is calling latency.get999thPercentile() - so it
would be less confusing if the first line of stress output were this:
{code}
total,interval_op_rate,interval_key_rate,latency,95th,99.9th,elapsed_time
{code}
Listing 99.9th instead of 99th.
--
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-5288) stress percentile label does not match what is returned
[ https://issues.apache.org/jira/browse/CASSANDRA-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751665#comment-13751665 ] Ryan McGuire commented on CASSANDRA-5288: - As in, we should change the heading, not the statistic. Too many things rely on that number the way it is. stress percentile label does not match what is returned --- Key: CASSANDRA-5288 URL: https://issues.apache.org/jira/browse/CASSANDRA-5288 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 1.2.2 Reporter: Chris Burroughs Assignee: Brandon Williams Priority: Minor We say it's the 99th: https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L65 But return 99.9th https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L145 Not sure which is intended. -- 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-4809) Allow restoring specific column families from archived commitlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751695#comment-13751695 ] Greg DeAngelis commented on CASSANDRA-4809: --- Are there any special considerations for system tables? Should they always be replayed regardless of what the user specifies to replay? Should this should be available as a property in commitlog_archiving.properties and the restore jmx call? Allow restoring specific column families from archived commitlog Key: CASSANDRA-4809 URL: https://issues.apache.org/jira/browse/CASSANDRA-4809 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 Reporter: Nick Bailey Labels: lhf Fix For: 2.0.1 Currently you can only restore the entire contents of a commit log archive. It would be useful to specify the keyspaces/column families you want to restore from an archived commitlog. -- 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-4809) Allow restoring specific column families from archived commitlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751733#comment-13751733 ] Jonathan Ellis commented on CASSANDRA-4809: --- That doesn't sound like a great idea to me. What if there was a DROP KEYSPACE in there that you don't want replayed? Allow restoring specific column families from archived commitlog Key: CASSANDRA-4809 URL: https://issues.apache.org/jira/browse/CASSANDRA-4809 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 Reporter: Nick Bailey Labels: lhf Fix For: 2.0.1 Currently you can only restore the entire contents of a commit log archive. It would be useful to specify the keyspaces/column families you want to restore from an archived commitlog. -- 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-4809) Allow restoring specific column families from archived commitlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751743#comment-13751743 ] Greg DeAngelis commented on CASSANDRA-4809: --- Ok gotcha, I'll take the keyspaces and column families to replay as provided. Allow restoring specific column families from archived commitlog Key: CASSANDRA-4809 URL: https://issues.apache.org/jira/browse/CASSANDRA-4809 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 Reporter: Nick Bailey Labels: lhf Fix For: 2.0.1 Currently you can only restore the entire contents of a commit log archive. It would be useful to specify the keyspaces/column families you want to restore from an archived commitlog. -- 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-5945) CAS transactions permitting multiple updates
[ https://issues.apache.org/jira/browse/CASSANDRA-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Persad updated CASSANDRA-5945: --- Attachment: TokenConsumptionTest.java CAS transactions permitting multiple updates Key: CASSANDRA-5945 URL: https://issues.apache.org/jira/browse/CASSANDRA-5945 Project: Cassandra Issue Type: Bug Components: Core Environment: 3 node Cassandra 2.0.0-rc2 cluster Java driver 1.0.2 Replication factor 3 Quorum consistency Reporter: Phil Persad Attachments: TokenConsumptionTest.java This bug is spawned off CASSANDRA-5925 to track an underlying issue not related to TTLs. To reproduce: Step 1: CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY (tkn)); Step 2: INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE); Step 3: UPDATE tkns SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE; Step 4: UPDATE tkns SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE; Repeat steps 2-4 about 100,000 times. Expectation: For the '[applied]' column in the result sets for steps 3 and 4, exactly one should be true and one should be false. Bug: In a small number of cases (varying from 0.002% to 1%) both updates will report success. See attached unit test. -- 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-5945) CAS transactions permitting multiple updates
Phil Persad created CASSANDRA-5945: -- Summary: CAS transactions permitting multiple updates Key: CASSANDRA-5945 URL: https://issues.apache.org/jira/browse/CASSANDRA-5945 Project: Cassandra Issue Type: Bug Components: Core Environment: 3 node Cassandra 2.0.0-rc2 cluster Java driver 1.0.2 Replication factor 3 Quorum consistency Reporter: Phil Persad Attachments: TokenConsumptionTest.java This bug is spawned off CASSANDRA-5925 to track an underlying issue not related to TTLs. To reproduce: Step 1: CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY (tkn)); Step 2: INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE); Step 3: UPDATE tkns SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE; Step 4: UPDATE tkns SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE; Repeat steps 2-4 about 100,000 times. Expectation: For the '[applied]' column in the result sets for steps 3 and 4, exactly one should be true and one should be false. Bug: In a small number of cases (varying from 0.002% to 1%) both updates will report success. See attached unit test. -- 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-5925) Race condition in update lightweight transaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751750#comment-13751750
]
Phil Persad commented on CASSANDRA-5925:
I've updated my test to ensure uniqueness of the tokens and am still
experiencing failures. I've created CASSANDRA-5945 to track the issue so that
the fixes here can be committed.
Race condition in update lightweight transaction
Key: CASSANDRA-5925
URL: https://issues.apache.org/jira/browse/CASSANDRA-5925
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: 3 node Cassandra 2.0.0-rc2 cluster. Java driver 1.0.2.
Reporter: Phil Persad
Assignee: Sylvain Lebresne
Fix For: 2.0
Attachments: 5925.txt, TokenConsumptionTest.java
I'm building some tests for a Cassandra PoC. One scenario I need to test is
consumption of 1 time tokens. These tokens must be consumed exactly once.
The cluster involved is a 3 node cluster. All queries are run with
ConsistencyLevel.QUORUM. I'm using the following queries:
CREATE KEYSPACE IF NOT EXISTS test WITH replication = { 'class' :
'SimpleStrategy', 'replication_factor' : 3 };
CREATE TABLE IF NOT EXISTS tkns (tkn blob, consumed boolean, PRIMARY KEY
(tkn));
INSERT INTO tkns (tkn, consumed) VALUES (?,FALSE) USING TTL 30;
UPDATE tkns USING TTL 1 SET consumed = TRUE WHERE tkn = ? IF consumed = FALSE;
I use the '[applied]' column in the result set of the update statement to
determine whether the token has been successfully consumed or if the token is
being replayed.
My test involves concurrently executing many sets of 1 insert and 2 update
statements (using Session#execute on BoundStatemnts) then checking to make
sure that only one of the updates was applied.
When I run this test with relatively few iterations (~100) my results are
what I expect (exactly 1 update succeeds). At ~1000 iterations, I start
seeing both updates reporting success in 1-2% of cases. While my test is
running, I see corresponding error entries in the Cassandra log:
ERROR 15:34:53,583 Exception in thread Thread[MutationStage:522,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:474,5,main]
java.lang.NullPointerException
ERROR 15:34:53,584 Exception in thread Thread[MutationStage:536,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:480,5,main]
java.lang.NullPointerException
ERROR 15:34:53,729 Exception in thread Thread[MutationStage:534,5,main]
java.lang.NullPointerException
Thanks.
Update:
I'm not sure what's going on with the logging the the dev release. I grabbed
the rc2 source and built that. The resultant log is a bit more informative:
ERROR 11:53:38,967 Exception in thread Thread[MutationStage:114,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:32)
at
org.apache.cassandra.serializers.UUIDSerializer.deserialize(UUIDSerializer.java:26)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:142)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getUUID(UntypedResultSet.java:131)
at
org.apache.cassandra.db.SystemKeyspace.loadPaxosState(SystemKeyspace.java:785)
at
org.apache.cassandra.service.paxos.PaxosState.commit(PaxosState.java:118)
at
org.apache.cassandra.service.paxos.CommitVerbHandler.doVerb(CommitVerbHandler.java:34)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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-5946) Commit Logs referencing deleted CFIDs not handled properly
Rick Branson created CASSANDRA-5946: --- Summary: Commit Logs referencing deleted CFIDs not handled properly Key: CASSANDRA-5946 URL: https://issues.apache.org/jira/browse/CASSANDRA-5946 Project: Cassandra Issue Type: Bug Components: Core Reporter: Rick Branson Assignee: Rick Branson ERROR 19:44:38,377 Exception in thread Thread[COMMIT-LOG-WRITER,5,main] java.lang.NullPointerException at org.apache.cassandra.db.commitlog.CommitLogAllocator.flushOldestTables(CommitLogAllocator.java:299) at org.apache.cassandra.db.commitlog.CommitLogAllocator.fetchSegment(CommitLogAllocator.java:135) at org.apache.cassandra.db.commitlog.CommitLog.activateNextSegment(CommitLog.java:333) at org.apache.cassandra.db.commitlog.CommitLog.access$100(CommitLog.java:44) at org.apache.cassandra.db.commitlog.CommitLog$LogRecordAdder.run(CommitLog.java:377) at org.apache.cassandra.db.commitlog.PeriodicCommitLogExecutorService$1.runMayThrow(PeriodicCommitLogExecutorService.java:46) at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) at java.lang.Thread.run(Thread.java:679) Working up a test case / patch for this. -- 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-5947) Sampling bug in metrics-core-2.0.3.jar used by Cassandra
J.B. Langston created CASSANDRA-5947: Summary: Sampling bug in metrics-core-2.0.3.jar used by Cassandra Key: CASSANDRA-5947 URL: https://issues.apache.org/jira/browse/CASSANDRA-5947 Project: Cassandra Issue Type: Bug Reporter: J.B. Langston There is a sampling bug in the version of the metrics library we're using in Cassandra. See https://github.com/codahale/metrics/issues/421. ExponentiallyDecayingSample is used by the Timer's histogram that is used in stress tool, and according to [~brandon.williams] it is also in a few other places like the dynamic snitch. The statistical theory involved in this bug goes over my head so i'm not sure if this would bug would meaningfully affect its usage by Cassandra. One of the comments on the bug mentions that it affects slow sampling rates (10 samples/min was the example given). We're currently distributing metrics-core-2.0.3.jar and according to the release nodes, this bug is fixed in 2.1.3: http://metrics.codahale.com/about/release-notes/#v2-1-3-aug-06-2012 -- 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] [Assigned] (CASSANDRA-5947) Sampling bug in metrics-core-2.0.3.jar used by Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-5947: --- Assignee: Brandon Williams Sampling bug in metrics-core-2.0.3.jar used by Cassandra Key: CASSANDRA-5947 URL: https://issues.apache.org/jira/browse/CASSANDRA-5947 Project: Cassandra Issue Type: Bug Reporter: J.B. Langston Assignee: Brandon Williams There is a sampling bug in the version of the metrics library we're using in Cassandra. See https://github.com/codahale/metrics/issues/421. ExponentiallyDecayingSample is used by the Timer's histogram that is used in stress tool, and according to [~brandon.williams] it is also in a few other places like the dynamic snitch. The statistical theory involved in this bug goes over my head so i'm not sure if this would bug would meaningfully affect its usage by Cassandra. One of the comments on the bug mentions that it affects slow sampling rates (10 samples/min was the example given). We're currently distributing metrics-core-2.0.3.jar and according to the release nodes, this bug is fixed in 2.1.3: http://metrics.codahale.com/about/release-notes/#v2-1-3-aug-06-2012 -- 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-4809) Allow restoring specific column families from archived commitlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Yeksigian updated CASSANDRA-4809: -- Assignee: Carl Yeksigian Allow restoring specific column families from archived commitlog Key: CASSANDRA-4809 URL: https://issues.apache.org/jira/browse/CASSANDRA-4809 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 Reporter: Nick Bailey Assignee: Carl Yeksigian Labels: lhf Fix For: 2.0.1 Currently you can only restore the entire contents of a commit log archive. It would be useful to specify the keyspaces/column families you want to restore from an archived commitlog. -- 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-4809) Allow restoring specific column families from archived commitlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Yeksigian updated CASSANDRA-4809: -- Attachment: 4809.patch Here is a first cut that just skips over any non-specified commit log entries. Uses cassandra.readKeyspaceCommitlog and cassandra.readColumnFamilyCommitlog command line arguments to specify how to read commit log entries. Allow restoring specific column families from archived commitlog Key: CASSANDRA-4809 URL: https://issues.apache.org/jira/browse/CASSANDRA-4809 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 Reporter: Nick Bailey Assignee: Carl Yeksigian Labels: lhf Fix For: 2.0.1 Attachments: 4809.patch Currently you can only restore the entire contents of a commit log archive. It would be useful to specify the keyspaces/column families you want to restore from an archived commitlog. -- 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] [Resolved] (CASSANDRA-5288) stress percentile label does not match what is returned
[ https://issues.apache.org/jira/browse/CASSANDRA-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-5288. --- Resolution: Fixed Fix Version/s: 2.0.1 1.2.10 Assignee: Jonathan Ellis (was: Brandon Williams) Ninja'd. stress percentile label does not match what is returned --- Key: CASSANDRA-5288 URL: https://issues.apache.org/jira/browse/CASSANDRA-5288 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 1.2.2 Reporter: Chris Burroughs Assignee: Jonathan Ellis Priority: Minor Fix For: 1.2.10, 2.0.1 We say it's the 99th: https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L65 But return 99.9th https://github.com/apache/cassandra/blob/trunk/tools/stress/src/org/apache/cassandra/stress/StressAction.java#L145 Not sure which is intended. -- 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
[2/6] git commit: label 99.9th correctly
label 99.9th correctly Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/47b2cd66 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/47b2cd66 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/47b2cd66 Branch: refs/heads/cassandra-2.0 Commit: 47b2cd6620894bf0c4c4584036eab49a2e14a50e Parents: a4dd7aa Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:44:16 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:44:16 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/47b2cd66/tools/stress/src/org/apache/cassandra/stress/StressAction.java -- diff --git a/tools/stress/src/org/apache/cassandra/stress/StressAction.java b/tools/stress/src/org/apache/cassandra/stress/StressAction.java index 9adf92f..3668198 100644 --- a/tools/stress/src/org/apache/cassandra/stress/StressAction.java +++ b/tools/stress/src/org/apache/cassandra/stress/StressAction.java @@ -64,7 +64,7 @@ public class StressAction extends Thread int threadCount = client.getThreads(); Consumer[] consumers = new Consumer[threadCount]; - output.println(total,interval_op_rate,interval_key_rate,latency/95th/99th,elapsed_time); + output.println(total,interval_op_rate,interval_key_rate,latency/95th/99.9th,elapsed_time); int itemsPerThread = client.getKeysPerThread(); int modulo = client.getNumKeys() % threadCount;
[1/6] git commit: label 99.9th correctly
Updated Branches: refs/heads/cassandra-1.2 a4dd7aa39 - 47b2cd662 refs/heads/cassandra-2.0 1bc2fc597 - 2383430df refs/heads/trunk 748beafeb - a42d4cada label 99.9th correctly Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/47b2cd66 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/47b2cd66 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/47b2cd66 Branch: refs/heads/cassandra-1.2 Commit: 47b2cd6620894bf0c4c4584036eab49a2e14a50e Parents: a4dd7aa Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:44:16 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:44:16 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/47b2cd66/tools/stress/src/org/apache/cassandra/stress/StressAction.java -- diff --git a/tools/stress/src/org/apache/cassandra/stress/StressAction.java b/tools/stress/src/org/apache/cassandra/stress/StressAction.java index 9adf92f..3668198 100644 --- a/tools/stress/src/org/apache/cassandra/stress/StressAction.java +++ b/tools/stress/src/org/apache/cassandra/stress/StressAction.java @@ -64,7 +64,7 @@ public class StressAction extends Thread int threadCount = client.getThreads(); Consumer[] consumers = new Consumer[threadCount]; - output.println(total,interval_op_rate,interval_key_rate,latency/95th/99th,elapsed_time); + output.println(total,interval_op_rate,interval_key_rate,latency/95th/99.9th,elapsed_time); int itemsPerThread = client.getKeysPerThread(); int modulo = client.getNumKeys() % threadCount;
[3/6] git commit: label 99.9th correctly
label 99.9th correctly Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/47b2cd66 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/47b2cd66 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/47b2cd66 Branch: refs/heads/trunk Commit: 47b2cd6620894bf0c4c4584036eab49a2e14a50e Parents: a4dd7aa Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:44:16 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:44:16 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/47b2cd66/tools/stress/src/org/apache/cassandra/stress/StressAction.java -- diff --git a/tools/stress/src/org/apache/cassandra/stress/StressAction.java b/tools/stress/src/org/apache/cassandra/stress/StressAction.java index 9adf92f..3668198 100644 --- a/tools/stress/src/org/apache/cassandra/stress/StressAction.java +++ b/tools/stress/src/org/apache/cassandra/stress/StressAction.java @@ -64,7 +64,7 @@ public class StressAction extends Thread int threadCount = client.getThreads(); Consumer[] consumers = new Consumer[threadCount]; - output.println(total,interval_op_rate,interval_key_rate,latency/95th/99th,elapsed_time); + output.println(total,interval_op_rate,interval_key_rate,latency/95th/99.9th,elapsed_time); int itemsPerThread = client.getKeysPerThread(); int modulo = client.getNumKeys() % threadCount;
[4/6] git commit: merge from 1.2
merge from 1.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2383430d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2383430d Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2383430d Branch: refs/heads/trunk Commit: 2383430dfd520b9c94f7d20a631f71f209b0d248 Parents: 1bc2fc5 47b2cd6 Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:45:25 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:45:25 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2383430d/tools/stress/src/org/apache/cassandra/stress/StressAction.java -- diff --cc tools/stress/src/org/apache/cassandra/stress/StressAction.java index ea84647,3668198..7098d0b --- a/tools/stress/src/org/apache/cassandra/stress/StressAction.java +++ b/tools/stress/src/org/apache/cassandra/stress/StressAction.java @@@ -66,7 -64,7 +66,7 @@@ public class StressAction extends Threa int threadCount = client.getThreads(); Consumer[] consumers = new Consumer[threadCount]; - output.println(total,interval_op_rate,interval_key_rate,latency,95th,99th,elapsed_time); - output.println(total,interval_op_rate,interval_key_rate,latency/95th/99.9th,elapsed_time); ++ output.println(total,interval_op_rate,interval_key_rate,latency,95th,99.9th,elapsed_time); int itemsPerThread = client.getKeysPerThread(); int modulo = client.getNumKeys() % threadCount;
[5/6] git commit: merge from 1.2
merge from 1.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2383430d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2383430d Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2383430d Branch: refs/heads/cassandra-2.0 Commit: 2383430dfd520b9c94f7d20a631f71f209b0d248 Parents: 1bc2fc5 47b2cd6 Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:45:25 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:45:25 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2383430d/tools/stress/src/org/apache/cassandra/stress/StressAction.java -- diff --cc tools/stress/src/org/apache/cassandra/stress/StressAction.java index ea84647,3668198..7098d0b --- a/tools/stress/src/org/apache/cassandra/stress/StressAction.java +++ b/tools/stress/src/org/apache/cassandra/stress/StressAction.java @@@ -66,7 -64,7 +66,7 @@@ public class StressAction extends Threa int threadCount = client.getThreads(); Consumer[] consumers = new Consumer[threadCount]; - output.println(total,interval_op_rate,interval_key_rate,latency,95th,99th,elapsed_time); - output.println(total,interval_op_rate,interval_key_rate,latency/95th/99.9th,elapsed_time); ++ output.println(total,interval_op_rate,interval_key_rate,latency,95th,99.9th,elapsed_time); int itemsPerThread = client.getKeysPerThread(); int modulo = client.getNumKeys() % threadCount;
[6/6] git commit: Merge branch 'cassandra-2.0' into trunk
Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a42d4cad Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a42d4cad Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a42d4cad Branch: refs/heads/trunk Commit: a42d4cada7e7496bad301263ec52a5d9e97c824b Parents: 748beaf 2383430 Author: Jonathan Ellis jbel...@apache.org Authored: Tue Aug 27 22:45:37 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Tue Aug 27 22:45:37 2013 -0500 -- tools/stress/src/org/apache/cassandra/stress/StressAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/a42d4cad/tools/stress/src/org/apache/cassandra/stress/StressAction.java --
