[jira] [Created] (CASSANDRA-4145) NullPointerException when using sstableloader with PropertyFileSnitch configured
NullPointerException when using sstableloader with PropertyFileSnitch configured
Key: CASSANDRA-4145
URL: https://issues.apache.org/jira/browse/CASSANDRA-4145
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.6
Reporter: Ji Cheng
Priority: Minor
I got a NullPointerException when using sstableloader on 1.0.6. The cluster is
using PropertyFileSnitch. The same configuration file is used for
sstableloader.
The problem is if StorageService is initialized before DatabaseDescriptor,
PropertyFileSnitch will try to access StorageService.instance before it
finishes initialization.
{code}
ERROR 01:14:05,601 Fatal configuration error
org.apache.cassandra.config.ConfigurationException: Error instantiating snitch
class 'org.apache.cassandra.locator.PropertyFileSnitch'.
at
org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:607)
at
org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:454)
at
org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:306)
at
org.apache.cassandra.service.StorageService.(StorageService.java:187)
at
org.apache.cassandra.service.StorageService.(StorageService.java:190)
at
org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:183)
at
org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:106)
at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:62)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at
org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:589)
... 7 more
Caused by: java.lang.NullPointerException
at
org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170)
at
org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60)
... 12 more
Error instantiating snitch class
'org.apache.cassandra.locator.PropertyFileSnitch'.
Fatal configuration error; unable to start server. See log for stacktrace.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4145) NullPointerException when using sstableloader with PropertyFileSnitch configured
[
https://issues.apache.org/jira/browse/CASSANDRA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ji Cheng updated CASSANDRA-4145:
Attachment: 4145.txt
> NullPointerException when using sstableloader with PropertyFileSnitch
> configured
>
>
> Key: CASSANDRA-4145
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4145
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.0.6
>Reporter: Ji Cheng
>Priority: Minor
> Attachments: 4145.txt
>
>
> I got a NullPointerException when using sstableloader on 1.0.6. The cluster
> is using PropertyFileSnitch. The same configuration file is used for
> sstableloader.
> The problem is if StorageService is initialized before DatabaseDescriptor,
> PropertyFileSnitch will try to access StorageService.instance before it
> finishes initialization.
> {code}
> ERROR 01:14:05,601 Fatal configuration error
> org.apache.cassandra.config.ConfigurationException: Error instantiating
> snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'.
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:607)
> at
> org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:454)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:306)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:187)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:190)
> at
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:183)
> at
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:106)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:62)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:589)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170)
> at
> org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60)
> ... 12 more
> Error instantiating snitch class
> 'org.apache.cassandra.locator.PropertyFileSnitch'.
> Fatal configuration error; unable to start server. See log for stacktrace.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3636) cassandra 1.0.x breakes APT on debian OpenVZ
[
https://issues.apache.org/jira/browse/CASSANDRA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253203#comment-13253203
]
Patrik Modesto commented on CASSANDRA-3636:
---
Hi, it's still a problem for cassandra 1.0.9 and openvz 3.0.23 on Debian
Squeeze.
> cassandra 1.0.x breakes APT on debian OpenVZ
>
>
> Key: CASSANDRA-3636
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3636
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Affects Versions: 1.0.6
> Environment: Debian Linux (stable), OpenVZ container
>Reporter: Zenek Kraweznik
>Assignee: Brandon Williams
>Priority: Minor
>
> During upgrade from 1.0.6
> {code}Setting up cassandra (1.0.6) ...
> *error: permission denied on key 'vm.max_map_count'*
> dpkg: error processing cassandra (--configure):
> subprocess installed post-installation script returned error exit status 255
> Errors were encountered while processing:
> cassandra
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3636) cassandra 1.0.x breakes APT on debian OpenVZ
[
https://issues.apache.org/jira/browse/CASSANDRA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrik Modesto updated CASSANDRA-3636:
--
Affects Version/s: 1.0.9
Added latest stable version of Cassandra.
> cassandra 1.0.x breakes APT on debian OpenVZ
>
>
> Key: CASSANDRA-3636
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3636
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Affects Versions: 1.0.6, 1.0.9
> Environment: Debian Linux (stable), OpenVZ container
>Reporter: Zenek Kraweznik
>Assignee: Brandon Williams
>Priority: Minor
>
> During upgrade from 1.0.6
> {code}Setting up cassandra (1.0.6) ...
> *error: permission denied on key 'vm.max_map_count'*
> dpkg: error processing cassandra (--configure):
> subprocess installed post-installation script returned error exit status 255
> Errors were encountered while processing:
> cassandra
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4146) Delete sstables on abnormal termination of sstableloader session
Delete sstables on abnormal termination of sstableloader session Key: CASSANDRA-4146 URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 Project: Cassandra Issue Type: Improvement Components: Tools Affects Versions: 1.0.9 Reporter: Manish Zope Fix For: 1.1.0 There are three cases where we have observed the abnormal termination 1) In case of exception while loading. 2) User terminates the loading process. 3) If some node is down OR un-reachable then sstableloader get stucked.In this case user have to terminate the process in between. In case of abnormal termination, sstables (which are added in this session) remains as it is on the cluster.In case user starts the process all over again by fixing the exception, it results in duplication of the data till Major compaction is triggered. sstableloader can maintain the session while loading the sstables in cluster.So in case of abnormal termination sstableloader triggers the event that will delete the sstables loaded in that session. Also It would be great to have timeout in case of sstableloader.That can be kept configurable. So if sstableloader process got stucked for period longer than timeout, it can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) Delete sstables on abnormal termination of sstableloader session
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manish Zope updated CASSANDRA-4146: --- Remaining Estimate: 168h (was: 504h) Original Estimate: 168h (was: 504h) > Delete sstables on abnormal termination of sstableloader session > > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope > Labels: sstableloader, tools > Fix For: 1.1.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) Delete sstables on abnormal termination of sstableloader session
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manish Zope updated CASSANDRA-4146: --- Remaining Estimate: 48h (was: 168h) Original Estimate: 48h (was: 168h) > Delete sstables on abnormal termination of sstableloader session > > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope > Labels: sstableloader, tools > Fix For: 1.1.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) Delete sstables on abnormal termination of sstableloader session
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-4146: Reviewer: (was: jbellis) Priority: Minor (was: Major) Fix Version/s: (was: 1.1.0) 1.1.1 I don't think deleting the sstables is the right thing to do, since the loader didn't create those files, and they are potentially very expensive to recreate. However, I do understand that the loader not failing, nor being able to give any indication of failure is a problem, and now that we have CASSANDRA-4051 we can address that. > Delete sstables on abnormal termination of sstableloader session > > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope >Priority: Minor > Labels: sstableloader, tools > Fix For: 1.1.1 > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4147) cqlsh doesn't accept NULL as valid input
cqlsh doesn't accept NULL as valid input
Key: CASSANDRA-4147
URL: https://issues.apache.org/jira/browse/CASSANDRA-4147
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.0.8
Reporter: T Jake Luciani
Assignee: paul cannon
Priority: Minor
Fix For: 1.0.10
cqlsh:cfs> insert into foo (key,val1,val2)values('row2',NULL,NULL);
Bad Request: unable to make long from 'NULL'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Git Push Summary
Updated Tags: refs/tags/cassandra-1.1.0-rc1 [created] f64181983
Git Push Summary
Updated Tags: refs/tags/1.1.0-rc1-tentative [deleted] cbbf54910
[jira] [Commented] (CASSANDRA-4147) cqlsh doesn't accept NULL as valid input
[
https://issues.apache.org/jira/browse/CASSANDRA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253441#comment-13253441
]
Sylvain Lebresne commented on CASSANDRA-4147:
-
I don't think this is specific to cqlsh, it's just that CQL doesn't know about
null.
For CQL3, CASSANDRA-3783 has some plan to add some null support. For CQL2, I'm
not sure it's worth bothering adding it to the language (adding it to the
grammar and adding code to handle it). Unless you have a good reason to?
> cqlsh doesn't accept NULL as valid input
>
>
> Key: CASSANDRA-4147
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4147
> Project: Cassandra
> Issue Type: Bug
>Affects Versions: 1.0.8
>Reporter: T Jake Luciani
>Assignee: paul cannon
>Priority: Minor
> Fix For: 1.0.10
>
>
> cqlsh:cfs> insert into foo (key,val1,val2)values('row2',NULL,NULL);
> Bad Request: unable to make long from 'NULL'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4147) cqlsh doesn't accept NULL as valid input
[
https://issues.apache.org/jira/browse/CASSANDRA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253445#comment-13253445
]
Jonathan Ellis commented on CASSANDRA-4147:
---
Explicitly inserting a null doesn't make much sense either; to Cassandra/CQL,
null is the complete absence of a value. So we'll *return* a null if you ask
for column {{foo}} and no {{foo}} exists for a given row, but I can't think of
why you'd want to explicitly insert one. (And a row consisting entirely of
nulls wouldn't exist at all...)
> cqlsh doesn't accept NULL as valid input
>
>
> Key: CASSANDRA-4147
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4147
> Project: Cassandra
> Issue Type: Bug
>Affects Versions: 1.0.8
>Reporter: T Jake Luciani
>Assignee: paul cannon
>Priority: Minor
> Fix For: 1.0.10
>
>
> cqlsh:cfs> insert into foo (key,val1,val2)values('row2',NULL,NULL);
> Bad Request: unable to make long from 'NULL'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4147) cqlsh doesn't accept NULL as valid input
[
https://issues.apache.org/jira/browse/CASSANDRA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253456#comment-13253456
]
T Jake Luciani commented on CASSANDRA-4147:
---
It's really syntactic sugar for people coming from SQL land. Internally it
would just ignore it.
> cqlsh doesn't accept NULL as valid input
>
>
> Key: CASSANDRA-4147
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4147
> Project: Cassandra
> Issue Type: Bug
>Affects Versions: 1.0.8
>Reporter: T Jake Luciani
>Assignee: paul cannon
>Priority: Minor
> Fix For: 1.0.10
>
>
> cqlsh:cfs> insert into foo (key,val1,val2)values('row2',NULL,NULL);
> Bad Request: unable to make long from 'NULL'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-4145) NullPointerException when using sstableloader with PropertyFileSnitch configured
[
https://issues.apache.org/jira/browse/CASSANDRA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-4145.
---
Resolution: Fixed
lgtm, committed
> NullPointerException when using sstableloader with PropertyFileSnitch
> configured
>
>
> Key: CASSANDRA-4145
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4145
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Tools
>Affects Versions: 0.8.1
>Reporter: Ji Cheng
>Assignee: Ji Cheng
>Priority: Minor
> Labels: bulkloader
> Fix For: 1.0.10, 1.1.0
>
> Attachments: 4145.txt
>
>
> I got a NullPointerException when using sstableloader on 1.0.6. The cluster
> is using PropertyFileSnitch. The same configuration file is used for
> sstableloader.
> The problem is if StorageService is initialized before DatabaseDescriptor,
> PropertyFileSnitch will try to access StorageService.instance before it
> finishes initialization.
> {code}
> ERROR 01:14:05,601 Fatal configuration error
> org.apache.cassandra.config.ConfigurationException: Error instantiating
> snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'.
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:607)
> at
> org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:454)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:306)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:187)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:190)
> at
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:183)
> at
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:106)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:62)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:589)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170)
> at
> org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60)
> ... 12 more
> Error instantiating snitch class
> 'org.apache.cassandra.locator.PropertyFileSnitch'.
> Fatal configuration error; unable to start server. See log for stacktrace.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4145) NullPointerException when using sstableloader with PropertyFileSnitch configured
[
https://issues.apache.org/jira/browse/CASSANDRA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4145:
--
Component/s: Tools
> NullPointerException when using sstableloader with PropertyFileSnitch
> configured
>
>
> Key: CASSANDRA-4145
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4145
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Tools
>Affects Versions: 0.8.1
>Reporter: Ji Cheng
>Assignee: Ji Cheng
>Priority: Minor
> Labels: bulkloader
> Fix For: 1.0.10, 1.1.0
>
> Attachments: 4145.txt
>
>
> I got a NullPointerException when using sstableloader on 1.0.6. The cluster
> is using PropertyFileSnitch. The same configuration file is used for
> sstableloader.
> The problem is if StorageService is initialized before DatabaseDescriptor,
> PropertyFileSnitch will try to access StorageService.instance before it
> finishes initialization.
> {code}
> ERROR 01:14:05,601 Fatal configuration error
> org.apache.cassandra.config.ConfigurationException: Error instantiating
> snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'.
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:607)
> at
> org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:454)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:306)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:187)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:190)
> at
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:183)
> at
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:106)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:62)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:589)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170)
> at
> org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60)
> ... 12 more
> Error instantiating snitch class
> 'org.apache.cassandra.locator.PropertyFileSnitch'.
> Fatal configuration error; unable to start server. See log for stacktrace.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4145) NullPointerException when using sstableloader with PropertyFileSnitch configured
[
https://issues.apache.org/jira/browse/CASSANDRA-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4145:
--
Reviewer: jbellis
Affects Version/s: (was: 1.0.6)
0.8.1
Fix Version/s: 1.1.0
1.0.10
Assignee: Ji Cheng
Labels: bulkloader (was: )
> NullPointerException when using sstableloader with PropertyFileSnitch
> configured
>
>
> Key: CASSANDRA-4145
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4145
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Tools
>Affects Versions: 0.8.1
>Reporter: Ji Cheng
>Assignee: Ji Cheng
>Priority: Minor
> Labels: bulkloader
> Fix For: 1.0.10, 1.1.0
>
> Attachments: 4145.txt
>
>
> I got a NullPointerException when using sstableloader on 1.0.6. The cluster
> is using PropertyFileSnitch. The same configuration file is used for
> sstableloader.
> The problem is if StorageService is initialized before DatabaseDescriptor,
> PropertyFileSnitch will try to access StorageService.instance before it
> finishes initialization.
> {code}
> ERROR 01:14:05,601 Fatal configuration error
> org.apache.cassandra.config.ConfigurationException: Error instantiating
> snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'.
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:607)
> at
> org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:454)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:306)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:187)
> at
> org.apache.cassandra.service.StorageService.(StorageService.java:190)
> at
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:183)
> at
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:106)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:62)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:589)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170)
> at
> org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60)
> ... 12 more
> Error instantiating snitch class
> 'org.apache.cassandra.locator.PropertyFileSnitch'.
> Fatal configuration error; unable to start server. See log for stacktrace.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[3/16] git commit: Merge branch 'cassandra-1.1.0' into cassandra-1.1
Merge branch 'cassandra-1.1.0' into cassandra-1.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f57f1c07 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f57f1c07 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f57f1c07 Branch: refs/heads/cassandra-1.1 Commit: f57f1c07c21bdd27ca7c8f41a880602872a0658b Parents: 389e6cd 483a699 Author: Jonathan Ellis Authored: Fri Apr 13 10:35:33 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:33 2012 -0500 -- .rat-excludes |1 + CHANGES.txt|8 +--- build.xml |2 +- debian/changelog |6 ++ .../cassandra/locator/PropertyFileSnitch.java |3 ++- 5 files changed, 11 insertions(+), 9 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/f57f1c07/CHANGES.txt --
[2/16] git commit: Merge branch 'cassandra-1.1.0' into cassandra-1.1
Merge branch 'cassandra-1.1.0' into cassandra-1.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f57f1c07 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f57f1c07 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f57f1c07 Branch: refs/heads/trunk Commit: f57f1c07c21bdd27ca7c8f41a880602872a0658b Parents: 389e6cd 483a699 Author: Jonathan Ellis Authored: Fri Apr 13 10:35:33 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:33 2012 -0500 -- .rat-excludes |1 + CHANGES.txt|8 +--- build.xml |2 +- debian/changelog |6 ++ .../cassandra/locator/PropertyFileSnitch.java |3 ++- 5 files changed, 11 insertions(+), 9 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/f57f1c07/CHANGES.txt --
[11/16] git commit: fixing the config name
fixing the config name Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/389e6cd7 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/389e6cd7 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/389e6cd7 Branch: refs/heads/trunk Commit: 389e6cd72407bbe92e9edf5e30115cc94bf005fa Parents: 20bd828 Author: Vijay Parthasarathy Authored: Thu Apr 12 21:16:35 2012 -0700 Committer: Vijay Parthasarathy Committed: Thu Apr 12 21:16:35 2012 -0700 -- conf/cassandra.yaml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/389e6cd7/conf/cassandra.yaml -- diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 2f6a7da..14cc525 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -32,7 +32,7 @@ hinted_handoff_throttle_delay_in_ms: 1 # The following setting populates the page cache on memtable flush and compaction # WARNING: Enable this setting only when the whole node's data fits in memory. # Defaults to: false -# populate_buffer_cache_on_flush: false +# populate_io_cache_on_flush: false # authentication backend, implementing IAuthenticator; used to identify users authenticator: org.apache.cassandra.auth.AllowAllAuthenticator
[7/16] git commit: support PropertyFileSnitch in bulk loader patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
support PropertyFileSnitch in bulk loader
patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c7388130
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c7388130
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c7388130
Branch: refs/heads/cassandra-1.1.0
Commit: c738813098e4306f6e102526121820dbbb3ee648
Parents: 142e8c1
Author: Jonathan Ellis
Authored: Fri Apr 13 10:31:01 2012 -0500
Committer: Jonathan Ellis
Committed: Fri Apr 13 10:31:01 2012 -0500
--
CHANGES.txt|1 +
.../cassandra/locator/PropertyFileSnitch.java |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e2fc4de..26d0011 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.0.10
+ * support PropertyFileSnitch in bulk loader (CASSANDRA-4145)
* add auto_snapshot option allowing disabling snapshot before drop/truncate
(CASSANDRA-3710)
* allow short snitch names (CASSANDRA-4130)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
index f085a38..8ddebf8 100644
--- a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
+++ b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
@@ -167,6 +167,7 @@ public class PropertyFileSnitch extends
AbstractNetworkTopologySnitch
logger.debug("loaded network topology {}",
FBUtilities.toString(reloadedMap));
endpointMap = reloadedMap;
-StorageService.instance.getTokenMetadata().invalidateCaches();
+if (StorageService.instance != null) // null check tolerates circular
dependency; see CASSANDRA-4145
+StorageService.instance.getTokenMetadata().invalidateCaches();
}
}
[9/16] git commit: support PropertyFileSnitch in bulk loader patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
support PropertyFileSnitch in bulk loader
patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c7388130
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c7388130
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c7388130
Branch: refs/heads/cassandra-1.1
Commit: c738813098e4306f6e102526121820dbbb3ee648
Parents: 142e8c1
Author: Jonathan Ellis
Authored: Fri Apr 13 10:31:01 2012 -0500
Committer: Jonathan Ellis
Committed: Fri Apr 13 10:31:01 2012 -0500
--
CHANGES.txt|1 +
.../cassandra/locator/PropertyFileSnitch.java |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e2fc4de..26d0011 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.0.10
+ * support PropertyFileSnitch in bulk loader (CASSANDRA-4145)
* add auto_snapshot option allowing disabling snapshot before drop/truncate
(CASSANDRA-3710)
* allow short snitch names (CASSANDRA-4130)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
index f085a38..8ddebf8 100644
--- a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
+++ b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
@@ -167,6 +167,7 @@ public class PropertyFileSnitch extends
AbstractNetworkTopologySnitch
logger.debug("loaded network topology {}",
FBUtilities.toString(reloadedMap));
endpointMap = reloadedMap;
-StorageService.instance.getTokenMetadata().invalidateCaches();
+if (StorageService.instance != null) // null check tolerates circular
dependency; see CASSANDRA-4145
+StorageService.instance.getTokenMetadata().invalidateCaches();
}
}
[10/16] git commit: support PropertyFileSnitch in bulk loader patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
support PropertyFileSnitch in bulk loader
patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c7388130
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c7388130
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c7388130
Branch: refs/heads/trunk
Commit: c738813098e4306f6e102526121820dbbb3ee648
Parents: 142e8c1
Author: Jonathan Ellis
Authored: Fri Apr 13 10:31:01 2012 -0500
Committer: Jonathan Ellis
Committed: Fri Apr 13 10:31:01 2012 -0500
--
CHANGES.txt|1 +
.../cassandra/locator/PropertyFileSnitch.java |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e2fc4de..26d0011 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.0.10
+ * support PropertyFileSnitch in bulk loader (CASSANDRA-4145)
* add auto_snapshot option allowing disabling snapshot before drop/truncate
(CASSANDRA-3710)
* allow short snitch names (CASSANDRA-4130)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
index f085a38..8ddebf8 100644
--- a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
+++ b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
@@ -167,6 +167,7 @@ public class PropertyFileSnitch extends
AbstractNetworkTopologySnitch
logger.debug("loaded network topology {}",
FBUtilities.toString(reloadedMap));
endpointMap = reloadedMap;
-StorageService.instance.getTokenMetadata().invalidateCaches();
+if (StorageService.instance != null) // null check tolerates circular
dependency; see CASSANDRA-4145
+StorageService.instance.getTokenMetadata().invalidateCaches();
}
}
[5/16] git commit: merge from 1.0
merge from 1.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/483a6999 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/483a6999 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/483a6999 Branch: refs/heads/cassandra-1.1 Commit: 483a699928637dcb0e72785a21e5fa16769f9fb0 Parents: 2eaea5b c738813 Author: Jonathan Ellis Authored: Fri Apr 13 10:34:13 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:21 2012 -0500 -- CHANGES.txt|8 +--- .../cassandra/locator/PropertyFileSnitch.java |3 ++- 2 files changed, 3 insertions(+), 8 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/CHANGES.txt -- diff --cc CHANGES.txt index 4ef47c5,26d0011..f09a470 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,5 +1,20 @@@ -1.0.10 +1.1-dev + * fix read_repair_chance to really default to 0.1 in the cli (CASSANDRA-4114) + * Adds caching and bloomFilterFpChange to CQL options (CASSANDRA-4042) + * Adds posibility to autoconfigure size of the KeyCache (CASSANDRA-4087) + * fix KEYS index from skipping results (CASSANDRA-3996) + * Remove sliced_buffer_size_in_kb dead option (CASSANDRA-4076) + * make loadNewSStable preserve sstable version (CASSANDRA-4077) + * Respect 1.0 cache settings as much as possible when upgrading + (CASSANDRA-4088) + * relax path length requirement for sstable files when upgrading on + non-Windows platforms (CASSANDRA-4110) + * fix terminination of the stress.java when errors were encountered + (CASSANDRA-4128) + * Move CfDef and KsDef validation out of thrift (CASSANDRA-4037) + * Fix get_paged_slice (CASSANDRA-4136) + * CQL3: Support slice with exclusive start and stop (CASSANDRA-3785) - Merged from 1.0: + * support PropertyFileSnitch in bulk loader (CASSANDRA-4145) * add auto_snapshot option allowing disabling snapshot before drop/truncate (CASSANDRA-3710) * allow short snitch names (CASSANDRA-4130) http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java --
[1/16] git commit: Merge branch 'cassandra-1.1' into trunk
Updated Branches: refs/heads/cassandra-1.0 142e8c1a2 -> c73881309 refs/heads/cassandra-1.1 389e6cd72 -> f57f1c07c refs/heads/cassandra-1.1.0 2eaea5be9 -> 483a69992 refs/heads/trunk 0501cdd39 -> 2914f15a0 Merge branch 'cassandra-1.1' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2914f15a Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2914f15a Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2914f15a Branch: refs/heads/trunk Commit: 2914f15a007f8b7c0994fc61c97161dd32f9bbe6 Parents: 0501cdd f57f1c0 Author: Jonathan Ellis Authored: Fri Apr 13 10:35:42 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:42 2012 -0500 -- .rat-excludes |1 + CHANGES.txt|8 +--- build.xml |2 +- debian/changelog |6 ++ .../cassandra/locator/PropertyFileSnitch.java |3 ++- 5 files changed, 11 insertions(+), 9 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2914f15a/CHANGES.txt -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2914f15a/build.xml -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2914f15a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java --
[15/16] git commit: Update version for 1.1.0 RC1 release
Update version for 1.1.0 RC1 release Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cbbf5491 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cbbf5491 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/cbbf5491 Branch: refs/heads/trunk Commit: cbbf54910f7f98e9f4b944b984b2460f42cd50bd Parents: 34c1fc0 Author: Sylvain Lebresne Authored: Thu Apr 12 10:01:18 2012 +0200 Committer: Sylvain Lebresne Committed: Thu Apr 12 10:01:18 2012 +0200 -- .rat-excludes|1 + build.xml|2 +- debian/changelog |6 ++ 3 files changed, 8 insertions(+), 1 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/.rat-excludes -- diff --git a/.rat-excludes b/.rat-excludes index 9dc6311..f41d97a 100644 --- a/.rat-excludes +++ b/.rat-excludes @@ -30,3 +30,4 @@ doc/cql/CQL* build.properties.default test/data/legacy-sstables/** examples/pig/** +examples/hadoop_word_count/conf/log4j.properties http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/build.xml -- diff --git a/build.xml b/build.xml index 2286b27..ca83a0d 100644 --- a/build.xml +++ b/build.xml @@ -25,7 +25,7 @@ - + http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=tree"/> http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/debian/changelog -- diff --git a/debian/changelog b/debian/changelog index 01bf383..9c795f1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +cassandra (1.1.0~rc1) unstable; urgency=low + + * New Release Candidate + + -- Sylvain Lebresne Thu, 12 Apr 2012 09:59:27 +0200 + cassandra (1.1.0~beta2) unstable; urgency=low * New beta release
[16/16] git commit: Update version for 1.1.0 RC1 release
Update version for 1.1.0 RC1 release Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cbbf5491 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cbbf5491 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/cbbf5491 Branch: refs/heads/cassandra-1.1 Commit: cbbf54910f7f98e9f4b944b984b2460f42cd50bd Parents: 34c1fc0 Author: Sylvain Lebresne Authored: Thu Apr 12 10:01:18 2012 +0200 Committer: Sylvain Lebresne Committed: Thu Apr 12 10:01:18 2012 +0200 -- .rat-excludes|1 + build.xml|2 +- debian/changelog |6 ++ 3 files changed, 8 insertions(+), 1 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/.rat-excludes -- diff --git a/.rat-excludes b/.rat-excludes index 9dc6311..f41d97a 100644 --- a/.rat-excludes +++ b/.rat-excludes @@ -30,3 +30,4 @@ doc/cql/CQL* build.properties.default test/data/legacy-sstables/** examples/pig/** +examples/hadoop_word_count/conf/log4j.properties http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/build.xml -- diff --git a/build.xml b/build.xml index 2286b27..ca83a0d 100644 --- a/build.xml +++ b/build.xml @@ -25,7 +25,7 @@ - + http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=tree"/> http://git-wip-us.apache.org/repos/asf/cassandra/blob/cbbf5491/debian/changelog -- diff --git a/debian/changelog b/debian/changelog index 01bf383..9c795f1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +cassandra (1.1.0~rc1) unstable; urgency=low + + * New Release Candidate + + -- Sylvain Lebresne Thu, 12 Apr 2012 09:59:27 +0200 + cassandra (1.1.0~beta2) unstable; urgency=low * New beta release
[4/16] git commit: merge from 1.0
merge from 1.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/483a6999 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/483a6999 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/483a6999 Branch: refs/heads/trunk Commit: 483a699928637dcb0e72785a21e5fa16769f9fb0 Parents: 2eaea5b c738813 Author: Jonathan Ellis Authored: Fri Apr 13 10:34:13 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:21 2012 -0500 -- CHANGES.txt|8 +--- .../cassandra/locator/PropertyFileSnitch.java |3 ++- 2 files changed, 3 insertions(+), 8 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/CHANGES.txt -- diff --cc CHANGES.txt index 4ef47c5,26d0011..f09a470 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,5 +1,20 @@@ -1.0.10 +1.1-dev + * fix read_repair_chance to really default to 0.1 in the cli (CASSANDRA-4114) + * Adds caching and bloomFilterFpChange to CQL options (CASSANDRA-4042) + * Adds posibility to autoconfigure size of the KeyCache (CASSANDRA-4087) + * fix KEYS index from skipping results (CASSANDRA-3996) + * Remove sliced_buffer_size_in_kb dead option (CASSANDRA-4076) + * make loadNewSStable preserve sstable version (CASSANDRA-4077) + * Respect 1.0 cache settings as much as possible when upgrading + (CASSANDRA-4088) + * relax path length requirement for sstable files when upgrading on + non-Windows platforms (CASSANDRA-4110) + * fix terminination of the stress.java when errors were encountered + (CASSANDRA-4128) + * Move CfDef and KsDef validation out of thrift (CASSANDRA-4037) + * Fix get_paged_slice (CASSANDRA-4136) + * CQL3: Support slice with exclusive start and stop (CASSANDRA-3785) - Merged from 1.0: + * support PropertyFileSnitch in bulk loader (CASSANDRA-4145) * add auto_snapshot option allowing disabling snapshot before drop/truncate (CASSANDRA-3710) * allow short snitch names (CASSANDRA-4130) http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java --
[6/16] git commit: merge from 1.0
merge from 1.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/483a6999 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/483a6999 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/483a6999 Branch: refs/heads/cassandra-1.1.0 Commit: 483a699928637dcb0e72785a21e5fa16769f9fb0 Parents: 2eaea5b c738813 Author: Jonathan Ellis Authored: Fri Apr 13 10:34:13 2012 -0500 Committer: Jonathan Ellis Committed: Fri Apr 13 10:35:21 2012 -0500 -- CHANGES.txt|8 +--- .../cassandra/locator/PropertyFileSnitch.java |3 ++- 2 files changed, 3 insertions(+), 8 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/CHANGES.txt -- diff --cc CHANGES.txt index 4ef47c5,26d0011..f09a470 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,20 -1,5 +1,20 @@@ -1.0.10 +1.1-dev + * fix read_repair_chance to really default to 0.1 in the cli (CASSANDRA-4114) + * Adds caching and bloomFilterFpChange to CQL options (CASSANDRA-4042) + * Adds posibility to autoconfigure size of the KeyCache (CASSANDRA-4087) + * fix KEYS index from skipping results (CASSANDRA-3996) + * Remove sliced_buffer_size_in_kb dead option (CASSANDRA-4076) + * make loadNewSStable preserve sstable version (CASSANDRA-4077) + * Respect 1.0 cache settings as much as possible when upgrading + (CASSANDRA-4088) + * relax path length requirement for sstable files when upgrading on + non-Windows platforms (CASSANDRA-4110) + * fix terminination of the stress.java when errors were encountered + (CASSANDRA-4128) + * Move CfDef and KsDef validation out of thrift (CASSANDRA-4037) + * Fix get_paged_slice (CASSANDRA-4136) + * CQL3: Support slice with exclusive start and stop (CASSANDRA-3785) - Merged from 1.0: + * support PropertyFileSnitch in bulk loader (CASSANDRA-4145) * add auto_snapshot option allowing disabling snapshot before drop/truncate (CASSANDRA-3710) * allow short snitch names (CASSANDRA-4130) http://git-wip-us.apache.org/repos/asf/cassandra/blob/483a6999/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java --
[8/16] git commit: support PropertyFileSnitch in bulk loader patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
support PropertyFileSnitch in bulk loader
patch by Ji Cheng; reviewed by jbellis for CASSANDRA-4145
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c7388130
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c7388130
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/c7388130
Branch: refs/heads/cassandra-1.0
Commit: c738813098e4306f6e102526121820dbbb3ee648
Parents: 142e8c1
Author: Jonathan Ellis
Authored: Fri Apr 13 10:31:01 2012 -0500
Committer: Jonathan Ellis
Committed: Fri Apr 13 10:31:01 2012 -0500
--
CHANGES.txt|1 +
.../cassandra/locator/PropertyFileSnitch.java |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e2fc4de..26d0011 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.0.10
+ * support PropertyFileSnitch in bulk loader (CASSANDRA-4145)
* add auto_snapshot option allowing disabling snapshot before drop/truncate
(CASSANDRA-3710)
* allow short snitch names (CASSANDRA-4130)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/c7388130/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
index f085a38..8ddebf8 100644
--- a/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
+++ b/src/java/org/apache/cassandra/locator/PropertyFileSnitch.java
@@ -167,6 +167,7 @@ public class PropertyFileSnitch extends
AbstractNetworkTopologySnitch
logger.debug("loaded network topology {}",
FBUtilities.toString(reloadedMap));
endpointMap = reloadedMap;
-StorageService.instance.getTokenMetadata().invalidateCaches();
+if (StorageService.instance != null) // null check tolerates circular
dependency; see CASSANDRA-4145
+StorageService.instance.getTokenMetadata().invalidateCaches();
}
}
[12/16] git commit: make cache skipping optional patch by harishd; reviewed by Vijay for CASSANDRA-2635
make cache skipping optional
patch by harishd; reviewed by Vijay for CASSANDRA-2635
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/20bd8281
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/20bd8281
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/20bd8281
Branch: refs/heads/trunk
Commit: 20bd8281fab66852659201a76a9c525cdf64b710
Parents: c215a4c
Author: Vijay Parthasarathy
Authored: Thu Apr 12 20:54:47 2012 -0700
Committer: Vijay Parthasarathy
Committed: Thu Apr 12 20:54:47 2012 -0700
--
conf/cassandra.yaml|5 +
src/java/org/apache/cassandra/config/Config.java |1 +
.../cassandra/config/DatabaseDescriptor.java |7 +++
.../apache/cassandra/io/sstable/SSTableWriter.java |8 +---
4 files changed, 18 insertions(+), 3 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/20bd8281/conf/cassandra.yaml
--
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index 0d94b0b..2f6a7da 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -29,6 +29,11 @@ max_hint_window_in_ms: 360 # one hour
# Sleep this long after delivering each hint
hinted_handoff_throttle_delay_in_ms: 1
+# The following setting populates the page cache on memtable flush and
compaction
+# WARNING: Enable this setting only when the whole node's data fits in memory.
+# Defaults to: false
+# populate_buffer_cache_on_flush: false
+
# authentication backend, implementing IAuthenticator; used to identify users
authenticator: org.apache.cassandra.auth.AllowAllAuthenticator
http://git-wip-us.apache.org/repos/asf/cassandra/blob/20bd8281/src/java/org/apache/cassandra/config/Config.java
--
diff --git a/src/java/org/apache/cassandra/config/Config.java
b/src/java/org/apache/cassandra/config/Config.java
index 253594b..cb1847e 100644
--- a/src/java/org/apache/cassandra/config/Config.java
+++ b/src/java/org/apache/cassandra/config/Config.java
@@ -136,6 +136,7 @@ public class Config
public int row_cache_save_period = 0;
public int row_cache_keys_to_save = Integer.MAX_VALUE;
public String row_cache_provider =
ConcurrentLinkedHashCacheProvider.class.getSimpleName();
+public boolean populate_io_cache_on_flush = false;
private static boolean loadYaml = true;
private static boolean outboundBindAny = false;
http://git-wip-us.apache.org/repos/asf/cassandra/blob/20bd8281/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
--
diff --git a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
b/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
index e74ac13..b6a1d4e 100644
--- a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
+++ b/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
@@ -194,6 +194,8 @@ public class DatabaseDescriptor
if (conf.disk_access_mode == Config.DiskAccessMode.mmap)
MmappedSegmentedFile.initCleaner();
+ logger.debug("page_cache_hinting is " +
conf.populate_io_cache_on_flush);
+
/* Authentication and authorization backend, implementing
IAuthenticator and IAuthority */
if (conf.authenticator != null)
authenticator =
FBUtilities.construct(conf.authenticator, "authenticator");
@@ -1056,4 +1058,9 @@ public class DatabaseDescriptor
{
return conf.streaming_socket_timeout_in_ms;
}
+
+public static boolean populateIOCacheOnFlush()
+{
+return conf.populate_io_cache_on_flush;
+}
}
http://git-wip-us.apache.org/repos/asf/cassandra/blob/20bd8281/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
b/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
index b1fcc79..d74514f 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
@@ -90,14 +90,15 @@ public class SSTableWriter extends SSTable
dbuilder = SegmentedFile.getCompressedBuilder();
dataFile = CompressedSequentialWriter.open(getFilename(),
descriptor.filenameFor(Component.COMPRESSION_INFO),
- true,
+
!DatabaseDescriptor.populateIOCacheOnFlush(),
metadata.compressionPara
[13/16] git commit: remove intialCapacity from rowcache patch by Vijay; reviewed by xedin for CASSANDRA-4141
remove intialCapacity from rowcache
patch by Vijay; reviewed by xedin for CASSANDRA-4141
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2eaea5be
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2eaea5be
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2eaea5be
Branch: refs/heads/trunk
Commit: 2eaea5be96461b1d9e405d26229b9803a96d3abf
Parents: cbbf549
Author: Vijay Parthasarathy
Authored: Thu Apr 12 08:36:22 2012 -0700
Committer: Vijay Parthasarathy
Committed: Thu Apr 12 08:38:04 2012 -0700
--
.../cassandra/cache/ConcurrentLinkedHashCache.java |1 -
.../apache/cassandra/cache/SerializingCache.java |1 -
2 files changed, 0 insertions(+), 2 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/2eaea5be/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
--
diff --git a/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
b/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
index a1cf4ea..ad651eb 100644
--- a/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
+++ b/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
@@ -69,7 +69,6 @@ public class ConcurrentLinkedHashCache implements
ICache
{
ConcurrentLinkedHashMap map = new
ConcurrentLinkedHashMap.Builder()
.weigher(weigher)
-.initialCapacity(0)
.maximumWeightedCapacity(weightedCapacity)
.concurrencyLevel(DEFAULT_CONCURENCY_LEVEL)
.build();
http://git-wip-us.apache.org/repos/asf/cassandra/blob/2eaea5be/src/java/org/apache/cassandra/cache/SerializingCache.java
--
diff --git a/src/java/org/apache/cassandra/cache/SerializingCache.java
b/src/java/org/apache/cassandra/cache/SerializingCache.java
index 275130c..08fad20 100644
--- a/src/java/org/apache/cassandra/cache/SerializingCache.java
+++ b/src/java/org/apache/cassandra/cache/SerializingCache.java
@@ -65,7 +65,6 @@ public class SerializingCache implements ICache
.weigher(useMemoryWeigher
? createMemoryWeigher()
: Weighers.singleton())
- .initialCapacity(capacity)
.maximumWeightedCapacity(capacity)
.concurrencyLevel(DEFAULT_CONCURENCY_LEVEL)
.listener(listener)
[14/16] git commit: remove intialCapacity from rowcache patch by Vijay; reviewed by xedin for CASSANDRA-4141
remove intialCapacity from rowcache
patch by Vijay; reviewed by xedin for CASSANDRA-4141
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2eaea5be
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2eaea5be
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2eaea5be
Branch: refs/heads/cassandra-1.1
Commit: 2eaea5be96461b1d9e405d26229b9803a96d3abf
Parents: cbbf549
Author: Vijay Parthasarathy
Authored: Thu Apr 12 08:36:22 2012 -0700
Committer: Vijay Parthasarathy
Committed: Thu Apr 12 08:38:04 2012 -0700
--
.../cassandra/cache/ConcurrentLinkedHashCache.java |1 -
.../apache/cassandra/cache/SerializingCache.java |1 -
2 files changed, 0 insertions(+), 2 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/2eaea5be/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
--
diff --git a/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
b/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
index a1cf4ea..ad651eb 100644
--- a/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
+++ b/src/java/org/apache/cassandra/cache/ConcurrentLinkedHashCache.java
@@ -69,7 +69,6 @@ public class ConcurrentLinkedHashCache implements
ICache
{
ConcurrentLinkedHashMap map = new
ConcurrentLinkedHashMap.Builder()
.weigher(weigher)
-.initialCapacity(0)
.maximumWeightedCapacity(weightedCapacity)
.concurrencyLevel(DEFAULT_CONCURENCY_LEVEL)
.build();
http://git-wip-us.apache.org/repos/asf/cassandra/blob/2eaea5be/src/java/org/apache/cassandra/cache/SerializingCache.java
--
diff --git a/src/java/org/apache/cassandra/cache/SerializingCache.java
b/src/java/org/apache/cassandra/cache/SerializingCache.java
index 275130c..08fad20 100644
--- a/src/java/org/apache/cassandra/cache/SerializingCache.java
+++ b/src/java/org/apache/cassandra/cache/SerializingCache.java
@@ -65,7 +65,6 @@ public class SerializingCache implements ICache
.weigher(useMemoryWeigher
? createMemoryWeigher()
: Weighers.singleton())
- .initialCapacity(capacity)
.maximumWeightedCapacity(capacity)
.concurrencyLevel(DEFAULT_CONCURENCY_LEVEL)
.listener(listener)
svn commit: r1325835 - in /cassandra/site: publish/download/index.html src/settings.py
Author: slebresne Date: Fri Apr 13 16:40:18 2012 New Revision: 1325835 URL: http://svn.apache.org/viewvc?rev=1325835&view=rev Log: Update website for 1.1.0 RC1 release Modified: cassandra/site/publish/download/index.html cassandra/site/src/settings.py Modified: cassandra/site/publish/download/index.html URL: http://svn.apache.org/viewvc/cassandra/site/publish/download/index.html?rev=1325835&r1=1325834&r2=1325835&view=diff == --- cassandra/site/publish/download/index.html (original) +++ cassandra/site/publish/download/index.html Fri Apr 13 16:40:18 2012 @@ -101,16 +101,16 @@ Development Cassandra Server Releases (not production ready) - The latest development release is 1.1.0-beta2 (released on - 2012-3-27). + The latest development release is 1.1.0-rc1 (released on + 2012-04-13). -http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-bin.tar.gz";>apache-cassandra-1.1.0-beta2-bin.tar.gz -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-bin.tar.gz.asc";>PGP] -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-bin.tar.gz.md5";>MD5] -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-bin.tar.gz.sha1";>SHA1] +http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-bin.tar.gz";>apache-cassandra-1.1.0-rc1-bin.tar.gz +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-bin.tar.gz.asc";>PGP] +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-bin.tar.gz.md5";>MD5] +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-bin.tar.gz.sha1";>SHA1] @@ -189,10 +189,10 @@ -http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-src.tar.gz";>apache-cassandra-1.1.0-beta2-src.tar.gz -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-src.tar.gz.asc";>PGP] -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-src.tar.gz.md5";>MD5] -[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-beta2-src.tar.gz.sha1";>SHA1] +http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-src.tar.gz";>apache-cassandra-1.1.0-rc1-src.tar.gz +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-src.tar.gz.asc";>PGP] +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-src.tar.gz.md5";>MD5] +[http://www.apache.org/dist/cassandra/1.1.0/apache-cassandra-1.1.0-rc1-src.tar.gz.sha1";>SHA1] Modified: cassandra/site/src/settings.py URL: http://svn.apache.org/viewvc/cassandra/site/src/settings.py?rev=1325835&r1=1325834&r2=1325835&view=diff == --- cassandra/site/src/settings.py (original) +++ cassandra/site/src/settings.py Fri Apr 13 16:40:18 2012 @@ -100,8 +100,8 @@ class CassandraDef(object): veryoldstable_exists = True stable_version = '1.0.9' stable_release_date = '2012-04-06' -devel_version = '1.1.0-beta2' -devel_release_date = '2012-3-27' +devel_version = '1.1.0-rc1' +devel_release_date = '2012-04-13' devel_exists = True _apache_base_url = 'http://www.apache.org' _svn_base_url = 'https://svn.apache.org/repos/asf'
[jira] [Created] (CASSANDRA-4148) Explore commitlog compression
Explore commitlog compression - Key: CASSANDRA-4148 URL: https://issues.apache.org/jira/browse/CASSANDRA-4148 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Jonathan Ellis Priority: Minor Probably worth trading cpu for i/o, even sequential i/o. The wrinkle is that we probably can only compress our sync window at a time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4140) Build stress classes in a location that allows tools/stress/bin/stress to find them
[ https://issues.apache.org/jira/browse/CASSANDRA-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253583#comment-13253583 ] Jonathan Ellis commented on CASSANDRA-4140: --- How about tools/bin/stress? > Build stress classes in a location that allows tools/stress/bin/stress to > find them > --- > > Key: CASSANDRA-4140 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4140 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.2 >Reporter: Nick Bailey >Assignee: Vijay >Priority: Trivial > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4140.patch > > > Right now its hard to run stress from a checkout of trunk. You need to do > 'ant artifacts' and then run the stress tool in the generated artifacts. > A discussion on irc came up with the proposal to just move stress to the main > jar, but the stress/stressd bash scripts in bin/, and drop the tools > directory altogether. It will be easier for users to find that way and will > make running stress from a checkout much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4143) HH delivery should not be attempted when target node is down
[ https://issues.apache.org/jira/browse/CASSANDRA-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253585#comment-13253585 ] Jonathan Ellis commented on CASSANDRA-4143: --- (done for 1.0.10 + 1.1.0) > HH delivery should not be attempted when target node is down > > > Key: CASSANDRA-4143 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4143 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 1.0.9 >Reporter: Radim Kolar >Priority: Minor > > Look at this log fragment. Cassandra tries to do HH delivery every 10 minutes > even if host is marked down by gossip. > INFO [GossipTasks:1] 2012-04-12 03:01:55,040 Gossiper.java (line 818) > InetAddress /64.6.104.18 is now dead. > INFO [MemoryMeter:1] 2012-04-12 03:04:12,503 Memtable.java (line 186) > CFS(Keyspace='system', ColumnFamily='HintsColumnFamily') liveRatio is > 1.7635719581514129 (just-counted was 1.7635719581514129). calculation took > 224ms for 226 columns > WARN [MemoryMeter:1] 2012-04-12 03:08:48,995 Memtable.java (line 176) > setting live ratio to minimum of 1.0 instead of 0.8717337990312605 > INFO [MemoryMeter:1] 2012-04-12 03:08:48,995 Memtable.java (line 186) > CFS(Keyspace='system', ColumnFamily='HintsColumnFamily') liveRatio is > 1.7635719581514129 (just-counted was 1.0). calculation took 8ms for 738 > columns > INFO [HintedHandoff:1] 2012-04-12 03:09:31,269 HintedHandOffManager.java > (line 292) Endpoint /64.6.104.18 died before hint delivery, aborting > INFO [MemoryMeter:1] 2012-04-12 03:16:58,007 Memtable.java (line 186) > CFS(Keyspace='system', ColumnFamily='HintsColumnFamily') liveRatio is > 1.7635719581514129 (just-counted was 1.0055416029080733). calculation took > 19ms for 1762 columns > INFO [HintedHandoff:1] 2012-04-12 03:19:54,924 HintedHandOffManager.java > (line 292) Endpoint /64.6.104.18 died before hint delivery, aborting -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4004) Add support for ReversedType
[
https://issues.apache.org/jira/browse/CASSANDRA-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253587#comment-13253587
]
Jonathan Ellis commented on CASSANDRA-4004:
---
I think I'd prefer to move this into our "implementation extensions" section as
{{WITH CLUSTERING ORDERED BY (time DESC)}} or something similar.
I also don't see any code to account for, if we've already ordered it as DESC
in the clustering declaration, that's going to affect what we need to do for
ORDER BY DESC (or ASC).
> Add support for ReversedType
>
>
> Key: CASSANDRA-4004
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4004
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
>Reporter: Sylvain Lebresne
>Assignee: Sylvain Lebresne
>Priority: Trivial
> Fix For: 1.1.1
>
> Attachments: 4004.txt
>
>
> It would be nice to add a native syntax for the use of ReversedType. I'm sure
> there is anything in SQL that we inspired ourselves from, so I would propose
> something like:
> {noformat}
> CREATE TABLE timeseries (
> key text,
> time uuid,
> value text,
> PRIMARY KEY (key, time DESC)
> )
> {noformat}
> Alternatively, the DESC could also be put after the column name definition
> but one argument for putting it in the PK instead is that this only apply to
> keys.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4140) Build stress classes in a location that allows tools/stress/bin/stress to find them
[ https://issues.apache.org/jira/browse/CASSANDRA-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253650#comment-13253650 ] Vijay commented on CASSANDRA-4140: -- I can change the build.xml to copy the files to tools/bin/stress... But will work only for the installed binaries but for running it from the source (after stress-build) we still might need to do tools/stress/bin/stress else we might have to move around stuff, like Stress bin to a common tools/bin that might be confusing but i am fine either ways :)... Acceptable? > Build stress classes in a location that allows tools/stress/bin/stress to > find them > --- > > Key: CASSANDRA-4140 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4140 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.2 >Reporter: Nick Bailey >Assignee: Vijay >Priority: Trivial > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4140.patch > > > Right now its hard to run stress from a checkout of trunk. You need to do > 'ant artifacts' and then run the stress tool in the generated artifacts. > A discussion on irc came up with the proposal to just move stress to the main > jar, but the stress/stressd bash scripts in bin/, and drop the tools > directory altogether. It will be easier for users to find that way and will > make running stress from a checkout much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) Delete sstables on abnormal termination of sstableloader session
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-4146: Attachment: 4146.txt Patch to detect and report failures, as well as exit with a non-zero return code if this happens. Also cuts the FST attempts to 4, which causes about 28s of delay, instead of 8 which results in a ridiculous 8+ minutes. > Delete sstables on abnormal termination of sstableloader session > > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope >Priority: Minor > Labels: sstableloader, tools > Fix For: 1.1.1 > > Attachments: 4146.txt > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) sstableloader should detect and report failures
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-4146: Summary: sstableloader should detect and report failures (was: Delete sstables on abnormal termination of sstableloader session) > sstableloader should detect and report failures > --- > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope >Priority: Minor > Labels: sstableloader, tools > Fix For: 1.1.1 > > Attachments: 4146.txt > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-4146) sstableloader should detect and report failures
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-4146: --- Assignee: Brandon Williams > sstableloader should detect and report failures > --- > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope >Assignee: Brandon Williams >Priority: Minor > Labels: sstableloader, tools > Fix For: 1.1.1 > > Attachments: 4146.txt > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4149) Looks like Maximum amount of cache available in 1.1 is 2 GB
Looks like Maximum amount of cache available in 1.1 is 2 GB --- Key: CASSANDRA-4149 URL: https://issues.apache.org/jira/browse/CASSANDRA-4149 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.0 Reporter: Vijay The problem is that capacity is a Integer which can maximum hold 2 GB, I will post a fix to CLHM in the mean time we might want to remove the maximumWeightedCapacity code path (atleast for Serializing cache) and implement it in our code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4150) Looks like Maximum amount of cache available in 1.1 is 2 GB
Looks like Maximum amount of cache available in 1.1 is 2 GB --- Key: CASSANDRA-4150 URL: https://issues.apache.org/jira/browse/CASSANDRA-4150 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.0 Reporter: Vijay The problem is that capacity is a Integer which can maximum hold 2 GB, I will post a fix to CLHM in the mean time we might want to remove the maximumWeightedCapacity code path (atleast for Serializing cache) and implement it in our code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4150) Looks like Maximum amount of cache available in 1.1 is 2 GB
[ https://issues.apache.org/jira/browse/CASSANDRA-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253718#comment-13253718 ] Vijay commented on CASSANDRA-4150: -- issue: http://code.google.com/p/concurrentlinkedhashmap/issues/detail?id=33 created. > Looks like Maximum amount of cache available in 1.1 is 2 GB > --- > > Key: CASSANDRA-4150 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4150 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 1.1.0 >Reporter: Vijay > > The problem is that capacity is a Integer which can maximum hold 2 GB, > I will post a fix to CLHM in the mean time we might want to remove the > maximumWeightedCapacity code path (atleast for Serializing cache) and > implement it in our code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4140) Build stress classes in a location that allows tools/stress/bin/stress to find them
[ https://issues.apache.org/jira/browse/CASSANDRA-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253731#comment-13253731 ] Jonathan Ellis commented on CASSANDRA-4140: --- bq. Stress bin to a common tools/bin That's what I was referring to; I don't care where the .class or .jar files go. > Build stress classes in a location that allows tools/stress/bin/stress to > find them > --- > > Key: CASSANDRA-4140 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4140 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.2 >Reporter: Nick Bailey >Assignee: Vijay >Priority: Trivial > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4140.patch > > > Right now its hard to run stress from a checkout of trunk. You need to do > 'ant artifacts' and then run the stress tool in the generated artifacts. > A discussion on irc came up with the proposal to just move stress to the main > jar, but the stress/stressd bash scripts in bin/, and drop the tools > directory altogether. It will be easier for users to find that way and will > make running stress from a checkout much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4146) sstableloader should detect and report failures
[ https://issues.apache.org/jira/browse/CASSANDRA-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4146: -- Reviewer: yukim > sstableloader should detect and report failures > --- > > Key: CASSANDRA-4146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4146 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0.9 >Reporter: Manish Zope >Assignee: Brandon Williams >Priority: Minor > Labels: sstableloader, tools > Fix For: 1.1.1 > > Attachments: 4146.txt > > Original Estimate: 48h > Remaining Estimate: 48h > > There are three cases where we have observed the abnormal termination > 1) In case of exception while loading. > 2) User terminates the loading process. > 3) If some node is down OR un-reachable then sstableloader get stucked.In > this case user have to terminate the process in between. > In case of abnormal termination, sstables (which are added in this session) > remains as it is on the cluster.In case user starts the process all over > again by fixing the exception, it results in duplication of the data till > Major compaction is triggered. > sstableloader can maintain the session while loading the sstables in > cluster.So in case of abnormal termination sstableloader triggers the event > that will delete the sstables loaded in that session. > Also It would be great to have timeout in case of sstableloader.That can be > kept configurable. > So if sstableloader process got stucked for period longer than timeout, it > can terminate itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4079) Check SSTable range before running cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4079: -- Reviewer: slebresne (was: bcoverston) > Check SSTable range before running cleanup > -- > > Key: CASSANDRA-4079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4079 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Benjamin Coverston >Assignee: Jonathan Ellis >Priority: Minor > Labels: compaction > Fix For: 1.1.1 > > Attachments: 4079.txt > > > Before running a cleanup compaction on an SSTable we should check the range > to see if the SSTable falls into the range we want to remove. If it doesn't > we can just mark the SSTable as compacted and be done with it, if it does, we > can no-op. > Will not help with STCS, but for LCS, and perhaps some others we may see a > benefit here after topology changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-556: Assignee: Yuki Morishita > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Yuki Morishita >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3283) node is sending streams to itself during move operation
[ https://issues.apache.org/jira/browse/CASSANDRA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-3283. --- Resolution: Cannot Reproduce Fix Version/s: (was: 1.1.1) Reviewer: (was: thepaul) > node is sending streams to itself during move operation > --- > > Key: CASSANDRA-3283 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3283 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: linux debian stable (squeeze), cassandra 0.8.6, java 6 > Update 26 >Reporter: Zenek Kraweznik >Priority: Minor > > I'm moving node 10.10.10.231 from 113427455640312821154458202477256070485 to > 0. > ring: > Address DC RackStatus State LoadOwns > Token > > 127605887595351923798765477786913079296 > 10.10.10.232 datacenter1 rack1 Up Normal 148.7 GB50.00% > 42535295865117307932921825928971026432 > 10.10.10.233 datacenter1 rack1 Up Normal 156.77 GB 25.00% > 85070591730234615865843651857942052864 > 10.10.10.231 datacenter1 rack1 Up Moving 188.75 GB 16.67% > 113427455640312821154458202477256070485 > 10.10.10.234 datacenter1 rack1 Up Normal 94.89 GB8.33% > 127605887595351923798765477786913079296 > netstats from node1: > Streaming to: /10.10.10.234 >/var/lib/cassandra/data/testdb2/ChangeLog-g-30-Data.db sections=2 > progress=0/6859992288 - 0% >/var/lib/cassandra/data/testdb2/ChangeLogIndex-g-10-Data.db sections=1 > progress=0/15286 - 0% >/var/lib/cassandra/data/testdb/ChangeLogIndex-g-48-Data.db sections=1 > progress=0/90 - 0% >/var/lib/cassandra/data/testdb/Testcoll-g-107-Data.db sections=2 > progress=0/5276 - 0% >/var/lib/cassandra/data/testdb/Testcoll2-g-74-Data.db sections=2 > progress=0/470 - 0% >/var/lib/cassandra/data/testdb/ChangeLogIndex-g-47-Data.db sections=1 > progress=0/1156 - 0% >/var/lib/cassandra/data/testdb/Testcoll-g-106-Data.db sections=2 > progress=0/329027714 - 0% >/var/lib/cassandra/data/testdb/ChangeLog-g-61-Data.db sections=2 > progress=0/30212596 - 0% >/var/lib/cassandra/data/testdb3/Testcoll2-g-42-Data.db sections=2 > progress=0/774117 - 0% >/var/lib/cassandra/data/testdb3/ChangeLogIndex-g-10-Data.db sections=1 > progress=0/90 - 0% > Streaming to: /10.10.10.231 >/var/lib/cassandra/data/testdb2/Testcoll-g-30-Data.db sections=2 > progress=39059456000/87950308260 - 44% >/var/lib/cassandra/data/testdb2/ChangeLog-g-30-Data.db sections=2 > progress=0/7806077255 - 0% >/var/lib/cassandra/data/testdb2/ChangeLogIndex-g-10-Data.db sections=1 > progress=0/15286 - 0% >/var/lib/cassandra/data/testdb3/Testcoll2-g-42-Data.db sections=2 > progress=0/784033 - 0% >/var/lib/cassandra/data/testdb3/ChangeLogIndex-g-10-Data.db sections=1 > progress=0/90 - 0% >/var/lib/cassandra/data/testdb/ChangeLogIndex-g-48-Data.db sections=1 > progress=0/90 - 0% >/var/lib/cassandra/data/testdb/Testcoll-g-107-Data.db sections=2 > progress=0/10499 - 0% >/var/lib/cassandra/data/testdb/Testcoll2-g-74-Data.db sections=2 > progress=0/1042 - 0% >/var/lib/cassandra/data/testdb/ChangeLogIndex-g-47-Data.db sections=1 > progress=0/1156 - 0% >/var/lib/cassandra/data/testdb/Testcoll-g-106-Data.db sections=2 > progress=0/329965993 - 0% >/var/lib/cassandra/data/testdb/ChangeLog-g-61-Data.db sections=2 > progress=0/24633913 - 0% > Streaming from: /10.10.10.231 >testdb: /var/lib/cassandra/data/testdb/ChangeLogIndex-g-47-Data.db > sections=1 progress=0/1156 - 0% >testdb: /var/lib/cassandra/data/testdb/ChangeLogIndex-g-48-Data.db > sections=1 progress=0/90 - 0% >testdb: /var/lib/cassandra/data/testdb/ChangeLog-g-61-Data.db sections=2 > progress=0/24633913 - 0% >testdb3: /var/lib/cassandra/data/testdb3/Testcoll2-g-42-Data.db sections=2 > progress=0/784033 - 0% >testdb: /var/lib/cassandra/data/testdb/Testcoll2-g-74-Data.db sections=2 > progress=0/1042 - 0% >testdb3: /var/lib/cassandra/data/testdb3/ChangeLogIndex-g-10-Data.db > sections=1 progress=0/90 - 0% >testdb2: /var/lib/cassandra/data/testdb2/ChangeLog-g-30-Data.db sections=2 > progress=0/7806077255 - 0% >testdb2: /var/lib/cassandra/data/testdb2/ChangeLogIndex-g-10-Data.db > sections=1 progress=0/15286 - 0% >testdb: /var/lib/cassandra/data/testdb/Testcoll-g-106-Data.db sections=2 > progress=0/329965993 - 0% >testdb2: /var/lib/cassandra/data/testdb2/Testcoll-g-30-Data.db sections=2 > progress=39059456000/87950308260 - 44% >testdb: /var/lib/cassandra/data/testdb/Testcoll-g-107-Data.db sections=2 > progress=0/10499 - 0% > Pool NameA
[jira] [Assigned] (CASSANDRA-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-556: Assignee: Dave Brosius (was: Yuki Morishita) Could you have a look at this, Dave? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-3946) BulkRecordWriter shouldn't stream any empty data/index files that might be created at end of flush
[ https://issues.apache.org/jira/browse/CASSANDRA-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-3946: - Assignee: Yuki Morishita (was: Brandon Williams) Yuki, does anything look suspicious in BulkRecordWriter for zero-length file creation? > BulkRecordWriter shouldn't stream any empty data/index files that might be > created at end of flush > -- > > Key: CASSANDRA-3946 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3946 > Project: Cassandra > Issue Type: Bug >Reporter: Chris Goffinet >Assignee: Yuki Morishita >Priority: Minor > Fix For: 1.1.1 > > Attachments: > 0001-CASSANDRA-3946-BulkRecordWriter-shouldn-t-stream-any.patch > > > If by chance, we flush sstables during BulkRecordWriter (we have seen it > happen), I want to make sure we don't try to stream them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4009) Increase usage of Metrics and flesh out o.a.c.metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4009: -- Reviewer: brandon.williams Assignee: Yuki Morishita (was: Brandon Williams) > Increase usage of Metrics and flesh out o.a.c.metrics > - > > Key: CASSANDRA-4009 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4009 > Project: Cassandra > Issue Type: Improvement >Reporter: Brandon Williams >Assignee: Yuki Morishita > Fix For: 1.1.1 > > > With CASSANDRA-3671 we have begun using the Metrics packages to expose stats > in a new JMX structure, intended to be more user-friendly (for example, you > don't need to know what a StorageProxy is or does.) This ticket serves as a > parent for subtasks to finish fleshing out the rest of the enhanced metrics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3946) BulkRecordWriter shouldn't stream any empty data/index files that might be created at end of flush
[ https://issues.apache.org/jira/browse/CASSANDRA-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253757#comment-13253757 ] Brandon Williams commented on CASSANDRA-3946: - I suspect if there is a problem here it's actually in UnsortedSimpleSSTableWriter. > BulkRecordWriter shouldn't stream any empty data/index files that might be > created at end of flush > -- > > Key: CASSANDRA-3946 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3946 > Project: Cassandra > Issue Type: Bug >Reporter: Chris Goffinet >Assignee: Yuki Morishita >Priority: Minor > Fix For: 1.1.1 > > Attachments: > 0001-CASSANDRA-3946-BulkRecordWriter-shouldn-t-stream-any.patch > > > If by chance, we flush sstables during BulkRecordWriter (we have seen it > happen), I want to make sure we don't try to stream them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4138) Add varint encoding to Serializing Cache
[ https://issues.apache.org/jira/browse/CASSANDRA-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253761#comment-13253761 ] Jonathan Ellis commented on CASSANDRA-4138: --- Couldn't we just extend DataOutputStream instead of introducing ADOS? (Pretty sure AbstractDataInput was a mistake as well.) > Add varint encoding to Serializing Cache > > > Key: CASSANDRA-4138 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4138 > Project: Cassandra > Issue Type: Sub-task > Components: Core >Affects Versions: 1.2 >Reporter: Vijay >Assignee: Vijay >Priority: Minor > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4138-Take1.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4045) BOF fails when some nodes are down
[ https://issues.apache.org/jira/browse/CASSANDRA-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-4045: Attachment: 4045.txt Patch requires CASSANDRA-4146. It would be nice if we could support the notion of consistency level here, but it's not as easy as setting a ConsistencyLevel directive like other output formats, so instead we just allow defining a maximum number of hosts that are allowed to fail before the entire job fails, and default that to zero. > BOF fails when some nodes are down > -- > > Key: CASSANDRA-4045 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4045 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Brandon Williams >Assignee: Brandon Williams > Labels: hadoop > Fix For: 1.1.1 > > Attachments: 4045.txt > > > As the summary says, we should allow jobs to complete when some targets are > unavailable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4079) Check SSTable range before running cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253779#comment-13253779 ] Benjamin Coverston commented on CASSANDRA-4079: --- +1 on the revised patch > Check SSTable range before running cleanup > -- > > Key: CASSANDRA-4079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4079 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Benjamin Coverston >Assignee: Jonathan Ellis >Priority: Minor > Labels: compaction > Fix For: 1.1.1 > > Attachments: 4079.txt > > > Before running a cleanup compaction on an SSTable we should check the range > to see if the SSTable falls into the range we want to remove. If it doesn't > we can just mark the SSTable as compacted and be done with it, if it does, we > can no-op. > Will not help with STCS, but for LCS, and perhaps some others we may see a > benefit here after topology changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4138) Add varint encoding to Serializing Cache
[ https://issues.apache.org/jira/browse/CASSANDRA-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253790#comment-13253790 ] Vijay commented on CASSANDRA-4138: -- I did try it before copying the problem is that we cannot override writeInt() writeLong() and writeShort() because they are marked as final. http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/io/DataOutputStream.java#DataOutputStream.writeInt%28int%29 > Add varint encoding to Serializing Cache > > > Key: CASSANDRA-4138 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4138 > Project: Cassandra > Issue Type: Sub-task > Components: Core >Affects Versions: 1.2 >Reporter: Vijay >Assignee: Vijay >Priority: Minor > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4138-Take1.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4045) BOF fails when some nodes are down
[ https://issues.apache.org/jira/browse/CASSANDRA-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4045: -- Reviewer: yukim > BOF fails when some nodes are down > -- > > Key: CASSANDRA-4045 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4045 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Brandon Williams >Assignee: Brandon Williams > Labels: hadoop > Fix For: 1.1.1 > > Attachments: 4045.txt > > > As the summary says, we should allow jobs to complete when some targets are > unavailable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-4150) Looks like Maximum amount of cache available in 1.1 is 2 GB
[ https://issues.apache.org/jira/browse/CASSANDRA-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay reassigned CASSANDRA-4150: Assignee: Vijay > Looks like Maximum amount of cache available in 1.1 is 2 GB > --- > > Key: CASSANDRA-4150 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4150 > Project: Cassandra > Issue Type: Bug > Components: Core >Affects Versions: 1.1.0 >Reporter: Vijay >Assignee: Vijay > > The problem is that capacity is a Integer which can maximum hold 2 GB, > I will post a fix to CLHM in the mean time we might want to remove the > maximumWeightedCapacity code path (atleast for Serializing cache) and > implement it in our code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4138) Add varint encoding to Serializing Cache
[ https://issues.apache.org/jira/browse/CASSANDRA-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253895#comment-13253895 ] Jonathan Ellis commented on CASSANDRA-4138: --- If we're relying on overriding writeInt etc, does that mean we're giving up being able to use varints over the network? (Not a concern for the cache obviously but I'm thinking ahead to CASSANDRA-3024.) > Add varint encoding to Serializing Cache > > > Key: CASSANDRA-4138 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4138 > Project: Cassandra > Issue Type: Sub-task > Components: Core >Affects Versions: 1.2 >Reporter: Vijay >Assignee: Vijay >Priority: Minor > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4138-Take1.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[cassandra-jdbc] 5 new revisions pushed by wfs...@gmail.com on 2012-04-13 22:19 GMT
5 new revisions:
Revision: 011d571d3de3
Author: Rick Shaw
Date: Fri Apr 13 14:02:00 2012
Log: Add additional entries to .gitignore
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=011d571d3de3
Revision: aad29d121d3e
Author: Rick Shaw
Date: Fri Apr 13 14:06:23 2012
Log: Resolve Issue #29. Remove log4j.properties
from .../main/resources...
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=aad29d121d3e
Revision: 2325f0a2ce41
Author: Rick Shaw
Date: Fri Apr 13 14:12:28 2012
Log: Update POM to use 1.0.9 release of C* dependencies.
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=2325f0a2ce41
Revision: 3213cf773012
Author: Rick Shaw
Date: Fri Apr 13 14:35:47 2012
Log: Resolve bad exception message from Issue #27
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=3213cf773012
Revision: 562b0f43d6a0
Author: Rick Shaw
Date: Fri Apr 13 15:18:35 2012
Log: Add log4j.properties back into /test/resources
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=562b0f43d6a0
==
Revision: 011d571d3de3
Author: Rick Shaw
Date: Fri Apr 13 14:02:00 2012
Log: Add additional entries to .gitignore
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=011d571d3de3
Modified:
/.gitignore
===
--- /.gitignore Thu Oct 13 01:56:25 2011
+++ /.gitignore Fri Apr 13 14:02:00 2012
@@ -1,9 +1,17 @@
*~
+.DS_Store
+.gitignore
.classpath
.project
.settings
+.externalToolBuilders
+.rat-excludes
+.svn/
.idea
*.iml
*.ipr
*.iws
-target
+target/
+build/
+bin/
+/build.properties
==
Revision: aad29d121d3e
Author: Rick Shaw
Date: Fri Apr 13 14:06:23 2012
Log: Resolve Issue #29. Remove log4j.properties from .../main/resources
Leave log4j.properties in .../test/resources
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=aad29d121d3e
Deleted:
/src/main/resources/log4j.properties
===
--- /src/main/resources/log4j.propertiesMon Nov 21 14:37:51 2011
+++ /dev/null
@@ -1,8 +0,0 @@
-# Test Log4J Properties File
-
-log4j.rootLogger=WARN, stdout
-log4j.logger.org.apache.cassandra.cql.jdbc=INFO
-
-log4j.appender.stdout=org.apache.log4j.ConsoleAppender
-log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
-log4j.appender.stdout.layout.ConversionPattern=%-6r %-5p [%-30c{3}] = %m%n
==
Revision: 2325f0a2ce41
Author: Rick Shaw
Date: Fri Apr 13 14:12:28 2012
Log: Update POM to use 1.0.9 release of C* dependencies.
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=2325f0a2ce41
Modified:
/pom.xml
===
--- /pom.xmlTue Dec 20 21:22:20 2011
+++ /pom.xmlFri Apr 13 14:12:28 2012
@@ -98,7 +98,7 @@
org.apache.cassandra
cassandra-thrift
- 1.0.6
+ 1.0.9
javax.servlet
@@ -113,7 +113,7 @@
org.apache.cassandra
cassandra-clientutil
- 1.0.6
+ 1.0.9
com.google.guava
==
Revision: 3213cf773012
Author: Rick Shaw
Date: Fri Apr 13 14:35:47 2012
Log: Resolve bad exception message from Issue #27.
Pass the originating exception rather than a the text message from
the exception which is apparently sometimes empty.
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=3213cf773012
Modified:
/src/main/java/org/apache/cassandra/cql/jdbc/CassandraStatement.java
===
--- /src/main/java/org/apache/cassandra/cql/jdbc/CassandraStatement.java
Mon Nov 21 14:56:04 2011
+++ /src/main/java/org/apache/cassandra/cql/jdbc/CassandraStatement.java
Fri Apr 13 14:35:47 2012
@@ -185,7 +185,7 @@
}
catch (TimedOutException e)
{
-throw new SQLTransientConnectionException(e.getMessage());
+throw new SQLTransientConnectionException(e);
}
catch (SchemaDisagreementException e)
{
@@ -193,7 +193,7 @@
}
catch (TException e)
{
-throw new SQLNonTransientConnectionException(e.getMessage());
+throw new SQLNonTransientConnectionException(e);
}
}
==
Revision: 562b0f43d6a0
Author: Rick Shaw
Date: Fri Apr 13 15:18:35 2012
Log: Add log4j.properties back into /test/resources
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?r=562b0f43d6a0
Modified:
[jira] [Commented] (CASSANDRA-4138) Add varint encoding to Serializing Cache
[ https://issues.apache.org/jira/browse/CASSANDRA-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253906#comment-13253906 ] Vijay commented on CASSANDRA-4138: -- Hi Jonathan, Nope this ticket was just an extension of the parent, i wanted to get the lhf first :)... Once we have EDOS we can use it for IVersionedSerializer.serialize(T t, EncodedDataOutput dos, int version) and OutboundTcpConnection.write(Message message, String id, EncodedDataOutput out) Which will be easier to deal with the version too (and with SST versioning)... Hope it makes sense. > Add varint encoding to Serializing Cache > > > Key: CASSANDRA-4138 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4138 > Project: Cassandra > Issue Type: Sub-task > Components: Core >Affects Versions: 1.2 >Reporter: Vijay >Assignee: Vijay >Priority: Minor > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4138-Take1.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4140) Build stress classes in a location that allows tools/stress/bin/stress to find them
[ https://issues.apache.org/jira/browse/CASSANDRA-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-4140: - Attachment: 0001-CASSANDRA-4140-v2.patch Done and tested! > Build stress classes in a location that allows tools/stress/bin/stress to > find them > --- > > Key: CASSANDRA-4140 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4140 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.2 >Reporter: Nick Bailey >Assignee: Vijay >Priority: Trivial > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4140-v2.patch, 0001-CASSANDRA-4140.patch > > > Right now its hard to run stress from a checkout of trunk. You need to do > 'ant artifacts' and then run the stress tool in the generated artifacts. > A discussion on irc came up with the proposal to just move stress to the main > jar, but the stress/stressd bash scripts in bin/, and drop the tools > directory altogether. It will be easier for users to find that way and will > make running stress from a checkout much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-4140) Build stress classes in a location that allows tools/stress/bin/stress to find them
[ https://issues.apache.org/jira/browse/CASSANDRA-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253918#comment-13253918 ] Vijay edited comment on CASSANDRA-4140 at 4/14/12 1:06 AM: --- Done! was (Author: vijay2...@yahoo.com): Done and tested! > Build stress classes in a location that allows tools/stress/bin/stress to > find them > --- > > Key: CASSANDRA-4140 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4140 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Affects Versions: 1.2 >Reporter: Nick Bailey >Assignee: Vijay >Priority: Trivial > Fix For: 1.2 > > Attachments: 0001-CASSANDRA-4140-v2.patch, 0001-CASSANDRA-4140.patch > > > Right now its hard to run stress from a checkout of trunk. You need to do > 'ant artifacts' and then run the stress tool in the generated artifacts. > A discussion on irc came up with the proposal to just move stress to the main > jar, but the stress/stressd bash scripts in bin/, and drop the tools > directory altogether. It will be easier for users to find that way and will > make running stress from a checkout much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4151) Apache project branding requirements: DOAP file [PATCH]
Apache project branding requirements: DOAP file [PATCH] --- Key: CASSANDRA-4151 URL: https://issues.apache.org/jira/browse/CASSANDRA-4151 Project: Cassandra Issue Type: Improvement Reporter: Shane Curcuru Attachments: doap_Cassandra.rdf Attached. Re: http://www.apache.org/foundation/marks/pmcs See Also: http://projects.apache.org/create.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4151) Apache project branding requirements: DOAP file [PATCH]
[ https://issues.apache.org/jira/browse/CASSANDRA-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru updated CASSANDRA-4151: - Attachment: doap_Cassandra.rdf > Apache project branding requirements: DOAP file [PATCH] > --- > > Key: CASSANDRA-4151 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4151 > Project: Cassandra > Issue Type: Improvement >Reporter: Shane Curcuru > Labels: branding > Attachments: doap_Cassandra.rdf > > > Attached. Re: http://www.apache.org/foundation/marks/pmcs > See Also: http://projects.apache.org/create.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-556) nodeprobe snapshot to support specific column families
[
https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius updated CASSANDRA-556:
---
Attachment: cf_snapshots_556.diff
Added a new command
snapshot_columnfamily keyspace columnfamily {-t snapshotname}
because hijacking the existing snapshot command is problematic, because
1) you can specify 1-n keyspaces so disambiquating what is the keyspace and
what is the column family is difficult.
2) a column family name could exist in multiple keyspaces.
applied in trunk
> nodeprobe snapshot to support specific column families
> --
>
> Key: CASSANDRA-556
> URL: https://issues.apache.org/jira/browse/CASSANDRA-556
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
>Reporter: Chris Were
>Assignee: Dave Brosius
>Priority: Minor
> Labels: lhf
> Fix For: 1.1.1
>
> Attachments: cf_snapshots_556.diff
>
>
> It would be good to support dumping specific column families via nodeprobe
> for backup purposes.
> In my particular case the majority of cassandra data doesn't need to be
> backed up except for a couple of column families containing user settings /
> profiles etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4152) cache the hashcode of DecoratedKey as it is immutable
cache the hashcode of DecoratedKey as it is immutable - Key: CASSANDRA-4152 URL: https://issues.apache.org/jira/browse/CASSANDRA-4152 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Dave Brosius Priority: Trivial Attachments: cache_decoratedkey_hash.diff cache the hashcode of the DecoratedKey on first hashCode() call. DecoratedKey is immutable so no need to run thru all ByteBuffer bytes of the key and do hashcode math. applied to trunk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4152) cache the hashcode of DecoratedKey as it is immutable
[ https://issues.apache.org/jira/browse/CASSANDRA-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Brosius updated CASSANDRA-4152: Attachment: cache_decoratedkey_hash.diff > cache the hashcode of DecoratedKey as it is immutable > - > > Key: CASSANDRA-4152 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4152 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Dave Brosius >Priority: Trivial > Attachments: cache_decoratedkey_hash.diff > > > cache the hashcode of the DecoratedKey on first hashCode() call. DecoratedKey > is immutable so no need to run thru all ByteBuffer bytes of the key and do > hashcode math. > applied to trunk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4152) cache the hashcode of DecoratedKey as it is immutable
[ https://issues.apache.org/jira/browse/CASSANDRA-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254006#comment-13254006 ] Stu Hood commented on CASSANDRA-4152: - Since I'm sure someone else will ask: "What did the benchmark look like?" > cache the hashcode of DecoratedKey as it is immutable > - > > Key: CASSANDRA-4152 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4152 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Dave Brosius >Priority: Trivial > Attachments: cache_decoratedkey_hash.diff > > > cache the hashcode of the DecoratedKey on first hashCode() call. DecoratedKey > is immutable so no need to run thru all ByteBuffer bytes of the key and do > hashcode math. > applied to trunk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
