[jira] [Updated] (CASSANDRA-6456) log listen address at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Bridges updated CASSANDRA-6456: Attachment: CASSANDRA-6456-3.patch > log listen address at startup > - > > Key: CASSANDRA-6456 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6456 > Project: Cassandra > Issue Type: Wish > Components: Core >Reporter: Jeremy Hanna >Assignee: Sean Bridges >Priority: Trivial > Attachments: CASSANDRA-6456-2.patch, CASSANDRA-6456-3.patch, > CASSANDRA-6456.patch > > > When looking through logs from a cluster, sometimes it's handy to know the > address a node is from the logs. It would be convenient if on startup, we > indicated the listen address for that node. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CASSANDRA-6456) log listen address at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862774#comment-13862774 ] Sean Bridges commented on CASSANDRA-6456: - New patch removes all lines covered by "this can go" > log listen address at startup > - > > Key: CASSANDRA-6456 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6456 > Project: Cassandra > Issue Type: Wish > Components: Core >Reporter: Jeremy Hanna >Assignee: Sean Bridges >Priority: Trivial > Attachments: CASSANDRA-6456-2.patch, CASSANDRA-6456-3.patch, > CASSANDRA-6456.patch > > > When looking through logs from a cluster, sometimes it's handy to know the > address a node is from the logs. It would be convenient if on startup, we > indicated the listen address for that node. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CASSANDRA-6505) counters++ global shards 2.0 back port
[
https://issues.apache.org/jira/browse/CASSANDRA-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862748#comment-13862748
]
Aleksey Yeschenko commented on CASSANDRA-6505:
--
Force-pushed the changes to the same branch.
> counters++ global shards 2.0 back port
> --
>
> Key: CASSANDRA-6505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6505
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
> Fix For: 2.0.5
>
>
> CASSANDRA-6504 introduces a new type of shard - 'global' - to 2.1. To enable
> live upgrade from 2.0 to 2.1, it's necessary that 2.0 nodes are able to
> understand the new 'global' shards in the counter contexts.
> 2.0 nodes will not produce 'global' shards, but must contain the merge logic.
> It isn't a trivial code change ("non-trivial code in a non-trivial part of
> the code"), hence this separate JIRA issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
git commit: RowIndexEntry.Serializer.skip is a static method, call it as such
Updated Branches:
refs/heads/trunk 59c996212 -> e674abe8e
RowIndexEntry.Serializer.skip is a static method, call it as such
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e674abe8
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e674abe8
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e674abe8
Branch: refs/heads/trunk
Commit: e674abe8eca6157b5c72c1dbdba2ecd122185274
Parents: 59c9962
Author: Dave Brosius
Authored: Sun Jan 5 20:03:06 2014 -0500
Committer: Dave Brosius
Committed: Sun Jan 5 20:03:06 2014 -0500
--
src/java/org/apache/cassandra/io/sstable/SSTableScanner.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/e674abe8/src/java/org/apache/cassandra/io/sstable/SSTableScanner.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableScanner.java
b/src/java/org/apache/cassandra/io/sstable/SSTableScanner.java
index 3dc0ded..34f9b98 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableScanner.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableScanner.java
@@ -139,7 +139,7 @@ public class SSTableScanner implements ICompactionScanner
}
else
{
-
sstable.metadata.comparator.rowIndexEntrySerializer().skip(ifile);
+RowIndexEntry.Serializer.skip(ifile);
}
}
}
[jira] [Commented] (CASSANDRA-5201) Cassandra/Hadoop does not support current Hadoop releases
[ https://issues.apache.org/jira/browse/CASSANDRA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862670#comment-13862670 ] Dmitriy V. Ryaboy commented on CASSANDRA-5201: -- The EB HadoopCompat is what we use in production at Twitter, and plan to keep up to date in the foreseeable future. Glad you are finding it useful. Maybe you can send that Reporter implementation as a pull request for hadoop-compat? Seems generally applicable. Thanks to this ping, I looked around and noticed that our Parquet project uses a slightly different version of the same code -- we'll take a look and merge things. Shouldn't change anything significantly for this patch. Also note that Tom White has a handy findbugs plugin to look for Hadoop incompatibility problems: https://github.com/tomwhite/hadoop-incompatibility-findbugs-detector Here's how you'd use it: https://github.com/Parquet/parquet-mr/pull/77/files > Cassandra/Hadoop does not support current Hadoop releases > - > > Key: CASSANDRA-5201 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5201 > Project: Cassandra > Issue Type: Bug > Components: Hadoop >Affects Versions: 1.2.0 >Reporter: Brian Jeltema >Assignee: Dave Brosius > Attachments: 5201_a.txt, hadoopCompat.patch > > > Using Hadoop 0.22.0 with Cassandra results in the stack trace below. > It appears that version 0.21+ changed org.apache.hadoop.mapreduce.JobContext > from a class to an interface. > Exception in thread "main" java.lang.IncompatibleClassChangeError: Found > interface org.apache.hadoop.mapreduce.JobContext, but class was expected > at > org.apache.cassandra.hadoop.ColumnFamilyInputFormat.getSplits(ColumnFamilyInputFormat.java:103) > at > org.apache.hadoop.mapreduce.JobSubmitter.writeNewSplits(JobSubmitter.java:445) > at > org.apache.hadoop.mapreduce.JobSubmitter.writeSplits(JobSubmitter.java:462) > at > org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357) > at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1045) > at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1042) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1153) > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1042) > at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1062) > at MyHadoopApp.run(MyHadoopApp.java:163) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:69) > at MyHadoopApp.main(MyHadoopApp.java:82) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.hadoop.util.RunJar.main(RunJar.java:192) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
