[
https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew F. Dennis updated CASSANDRA-1654:
-----------------------------------------
Attachment: 1654-cassandra-0.7-v3.txt
1654-cassandra-0.7-v3.txt adds the EC2Snitch info to Gossiper after Gossiper
has been initialized preventing the NPE above.
EC2Snitch is still not entirely working though.
{noformat}
ERROR [pool-1-thread-3] 2010-12-31 20:42:49,085 Cassandra.java (line 3044)
Internal error processing batch_mutate
java.lang.NullPointerException
at
org.apache.cassandra.locator.Ec2Snitch.getDatacenter(Ec2Snitch.java:76)
at
org.apache.cassandra.locator.DynamicEndpointSnitch.getDatacenter(DynamicEndpointSnitch.java:115)
at
org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:104)
at
org.apache.cassandra.thrift.CassandraServer.doInsert(CassandraServer.java:412)
at
org.apache.cassandra.thrift.CassandraServer.batch_mutate(CassandraServer.java:385)
at
org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.process(Cassandra.java:3036)
at
org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:2555)
at
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:167)
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)
{noformat}
> EC2Snitch
> ---------
>
> Key: CASSANDRA-1654
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1654
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Fix For: 0.7.1
>
> Attachments: 1654-cassandra-0.7-v3.txt, 1654-incomplete.txt,
> 1654-v2.txt, 1654.txt
>
>
> This will be a snitch extending AbstractNetworkTopologySnitch that pulls DC
> from instance metadata placement_availability_zone.
> I don't think we can get rack information so the choice is between picking
> something unique-per-machine to be the rack or assigning everything in the DC
> the same rack. Second seems easier, so let's use placement_availability_zone
> for rack, too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
