Build failed in Jenkins: Cassandra #1207

[Apache Jenkins Server]

See 

Changes:

[slebresne] merge from 1.0

[slebresne] Add missing file from previous commit

--
[...truncated 2243 lines...]
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.122 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.locator.ReplicationStrategyEndpointCacheTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.399 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.SimpleStrategyTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.545 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.345 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceCounterTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 1.982 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceCounterTest):
 Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceCounterTest 
FAILED
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceStandardTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 1.923 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceStandardTest):
Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceStandardTest 
FAILED
[junit] Testsuite: org.apache.cassandra.service.CassandraServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.35 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.service.ConsistencyLevelTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.734 sec
[junit] 
[junit] Testcase: 
testReadWriteConsistencyChecks(org.apache.cassandra.service.ConsistencyLevelTest):
Caused an ERROR
[junit] invalid consistency level: ANY
[junit] java.lang.UnsupportedOperationException: invalid consistency level: 
ANY
[junit] at 
org.apache.cassandra.service.ReadCallback.determineBlockFor(ReadCallback.java:195)
[junit] at 
org.apache.cassandra.service.ReadCallback.(ReadCallback.java:68)
[junit] at 
org.apache.cassandra.service.StorageProxy.getReadCallback(StorageProxy.java:798)
[junit] at 
org.apache.cassandra.service.ConsistencyLevelTest.testReadWriteConsistencyChecks(ConsistencyLevelTest.java:110)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.ConsistencyLevelTest FAILED
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] 
[junit] Testcase: 
org.apache.cassandra.service.EmbeddedCassandraServiceTest:BeforeFirstTest:  
  Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the 
report does not re

hintedhandoff in 1.0.3

[Radim Kolar]

I suspect these partial/invalid hints are left over from a failed 
hints delivery from before you upgraded to 1.0.3 and not something 
created by 1.0.3.
Try to clear HintsColumnFamily (by removing the sstables for example) 
first and then see if you still can reproduce this issue afterwards.
it still does not work, but there is an improvement over 1.0.2. 
currently it looks like this:


 INFO [HintedHandoff:1] 2011-11-15 06:42:59,794 
HintedHandOffManager.java (line 334) Finished hinted handoff of 0 rows 
to endpoint /


but there is lot of data not delivered. forced compaction shows it:

112) Compacting 
[SSTableReader(path='/var/lib/cassandra/data/system/HintsColumnFamily-hb-63-Data.db'), 
SSTableReader(path='/var/lib/cassandra/data/system/HintsColumnFamily-hb-61-Data.db')]
 INFO [CompactionExecutor:41] 2011-11-15 07:08:24,034 
CompactionController.java (line 129) Compacting large row 
system/HintsColumnFamily:0758480e325aa09951c555e1249a69ba (237411479 
bytes) incrementally
 INFO [CompactionExecutor:41] 2011-11-15 07:08:33,418 
CompactionTask.java (line 213) Compacted to 
[/var/lib/cassandra/data/system/HintsColumnFamily-hb-64-Data.db,].  
237,411,643 to 237,411,505 (~99% of original) bytes for 1 keys at 
24.091642MB/s.  Time: 9,398ms.


after node restart it still shows 0 rows delivered. hints should be 
newly written by 1.0.3. i deleted old rows from older versions in hints 
- only 2 tombstones left there before another batch of hints testing.


hints inside are not from supercolumn CF. I remember to have 2 rows in 
HintsColumnFamily, one was successfully delivered and this one seems to 
be stuck. These hints are older than 1 hour.


Did you tested outgoing hints delivery with more than row there? its 
probably 1 key = 1 hints delivery session and if node is back up for 
while then second hints session is created. Try to do your testing with 
about 500k hints with multiple sessions.

[VOTE] Release Apache Cassandra 1.0.3 (take 2)

[Sylvain Lebresne]

So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
Now that they are fixed, let's try again. I propose the following artifacts
for release as 1.0.3.

SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
Artifacts: 
https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-186/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~slebresne/

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/I1dZG (CHANGES.txt)
[2]: http://goo.gl/PeD3Z (NEWS.txt)

Re: hintedhandoff in 1.0.3

[Radim Kolar]

Same problem on other node:  2 keys in HintsColumnFamily. One delivered, 
one left.


 INFO [HintedHandoff:1] 2011-11-15 10:31:53,181 
HintedHandOffManager.java (line 268) Started hinted handoff for token: 
99070591730234615865843651857942052864
 INFO [HintedHandoff:1] 2011-11-15 10:32:49,385 ColumnFamilyStore.java 
(line 688) Enqueuing flush of 
Memtable-HintsColumnFamily@797897458(1674737/2093421 serialized/live 
bytes, 6176 ops)
 INFO [FlushWriter:5] 2011-11-15 10:32:49,386 Memtable.java (line 239) 
Writing Memtable-HintsColumnFamily@797897458(1674737/2093421 
serialized/live bytes, 6176 ops)
 INFO [CompactionExecutor:10] 2011-11-15 10:32:49,387 
CompactionTask.java (line 112) Compacting 
[SSTableReader(path='/usr/local/cassandra/data/system/HintsColumnFamily-hb-754-Data.db'), 
SSTableReader(path='/usr/local/cassandra/data/system/HintsColumnFamily-hb-752-Data.db')]
 INFO [FlushWriter:5] 2011-11-15 10:32:49,523 Memtable.java (line 275) 
Completed flushing 
/usr/local/cassandra/data/system/HintsColumnFamily-hb-755-Data.db 
(1888357 bytes)
 INFO [CompactionExecutor:10] 2011-11-15 10:32:49,820 
CompactionTask.java (line 213) Compacted to 
[/usr/local/cassandra/data/system/HintsColumnFamily-hb-756-Data.db,].  
19,913,818 to 19,913,392 (~99% of original) bytes for 2 keys at 
43.960395MB/s.  Time: 432ms.
 INFO [HintedHandoff:1] 2011-11-15 10:32:49,820 
HintedHandOffManager.java (line 334) Finished hinted handoff of 5796 rows

Re: [VOTE] Release Apache Cassandra 1.0.3 (take 2)

[Eric Evans]

On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne  wrote:
> So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
> Now that they are fixed, let's try again. I propose the following artifacts
> for release as 1.0.3.
>
> SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-186/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/I1dZG (CHANGES.txt)
> [2]: http://goo.gl/PeD3Z (NEWS.txt)
>

It looks like interface/cassandra.thrift has changed without the Java
code being regenerated.  The test_describe system test is failing
because of this, (the versions don't match).

Probably not justification for a re-roll, but not a great thing for
the release either...

-- 
Eric Evans
Acunu | http://www.acunu.com | @acunu

Re: [VOTE] Release Apache Cassandra 1.0.3 (take 2)

[Sylvain Lebresne]

Apparently the thrift version was bumped by CASSANDRA-3433 but after
the initial commit
and the code was never regenerated. Means that it's already in 1.0.2 I believe.

I guess I'll add 'regenerate the thrift bindings' before testing to my
release process.

--
Sylvain

On Tue, Nov 15, 2011 at 2:46 PM, Eric Evans  wrote:
> On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne  
> wrote:
>> So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
>> Now that they are fixed, let's try again. I propose the following artifacts
>> for release as 1.0.3.
>>
>> SVN: 
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
>> Artifacts: 
>> https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachecassandra-186/
>>
>> The artifacts as well as the debian package are also available here:
>> http://people.apache.org/~slebresne/
>>
>> The vote will be open for 72 hours (longer if needed).
>>
>> [1]: http://goo.gl/I1dZG (CHANGES.txt)
>> [2]: http://goo.gl/PeD3Z (NEWS.txt)
>>
>
> It looks like interface/cassandra.thrift has changed without the Java
> code being regenerated.  The test_describe system test is failing
> because of this, (the versions don't match).
>
> Probably not justification for a re-roll, but not a great thing for
> the release either...
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
>

Re: [VOTE] Release Apache Cassandra 1.0.3 (take 2)

[Jonathan Ellis]

If the java code wasn't rebuilt doesn't that mean whatever we tried to
add to cassandra.thrift, isn't actually available in this build?

On Tue, Nov 15, 2011 at 7:46 AM, Eric Evans  wrote:
> On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne  
> wrote:
>> So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
>> Now that they are fixed, let's try again. I propose the following artifacts
>> for release as 1.0.3.
>>
>> SVN: 
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
>> Artifacts: 
>> https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachecassandra-186/
>>
>> The artifacts as well as the debian package are also available here:
>> http://people.apache.org/~slebresne/
>>
>> The vote will be open for 72 hours (longer if needed).
>>
>> [1]: http://goo.gl/I1dZG (CHANGES.txt)
>> [2]: http://goo.gl/PeD3Z (NEWS.txt)
>>
>
> It looks like interface/cassandra.thrift has changed without the Java
> code being regenerated.  The test_describe system test is failing
> because of this, (the versions don't match).
>
> Probably not justification for a re-roll, but not a great thing for
> the release either...
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: [VOTE] Release Apache Cassandra 1.0.3 (take 2)

[Eric Evans]

On Tue, Nov 15, 2011 at 8:29 AM, Jonathan Ellis  wrote:
> If the java code wasn't rebuilt doesn't that mean whatever we tried to
> add to cassandra.thrift, isn't actually available in this build?

It looks like r1195644 is where all the actual changes took place, and
r1195646 followed that up with the corresponding version update.  Code
was generated (and committed) for the former but not the latter.

> On Tue, Nov 15, 2011 at 7:46 AM, Eric Evans  wrote:
>> On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne  
>> wrote:
>>> So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
>>> Now that they are fixed, let's try again. I propose the following artifacts
>>> for release as 1.0.3.
>>>
>>> SVN: 
>>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
>>> Artifacts: 
>>> https://repository.apache.org/content/repositories/orgapachecassandra-186/org/apache/cassandra/apache-cassandra/1.0.3/
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachecassandra-186/
>>>
>>> The artifacts as well as the debian package are also available here:
>>> http://people.apache.org/~slebresne/
>>>
>>> The vote will be open for 72 hours (longer if needed).
>>>
>>> [1]: http://goo.gl/I1dZG (CHANGES.txt)
>>> [2]: http://goo.gl/PeD3Z (NEWS.txt)
>>>
>>
>> It looks like interface/cassandra.thrift has changed without the Java
>> code being regenerated.  The test_describe system test is failing
>> because of this, (the versions don't match).
>>
>> Probably not justification for a re-roll, but not a great thing for
>> the release either...
>>
>> --
>> Eric Evans
>> Acunu | http://www.acunu.com | @acunu
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>



-- 
Eric Evans
Acunu | http://www.acunu.com | @acunu

Build failed in Jenkins: Cassandra-quick #123

[Apache Jenkins Server]

See 

Changes:

[jbellis] merge from 1.0

--
[...truncated 1585 lines...]
[junit] 
[junit] Testsuite: 
org.apache.cassandra.locator.OldNetworkTopologyStrategyTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.162 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.locator.ReplicationStrategyEndpointCacheTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.517 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.SimpleStrategyTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.703 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.453 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceCounterTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 2.642 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceCounterTest):
 Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceCounterTest 
FAILED
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceStandardTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 2.975 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceStandardTest):
Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceStandardTest 
FAILED
[junit] Testsuite: org.apache.cassandra.service.CassandraServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.459 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.service.ConsistencyLevelTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.902 sec
[junit] 
[junit] Testcase: 
testReadWriteConsistencyChecks(org.apache.cassandra.service.ConsistencyLevelTest):
Caused an ERROR
[junit] invalid consistency level: ANY
[junit] java.lang.UnsupportedOperationException: invalid consistency level: 
ANY
[junit] at 
org.apache.cassandra.service.ReadCallback.determineBlockFor(ReadCallback.java:195)
[junit] at 
org.apache.cassandra.service.ReadCallback.(ReadCallback.java:68)
[junit] at 
org.apache.cassandra.service.StorageProxy.getReadCallback(StorageProxy.java:798)
[junit] at 
org.apache.cassandra.service.ConsistencyLevelTest.testReadWriteConsistencyChecks(ConsistencyLevelTest.java:110)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.ConsistencyLevelTest FAILED
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] 
[junit] Testcase: 
org.apache.cassandra.service.EmbeddedCassandraServiceTest:BeforeFirstTest:  
  Caused an ERROR
[junit] Forked Java VM exited abnormall

Build failed in Jenkins: Cassandra #1208

[Apache Jenkins Server]

See 

Changes:

[jbellis] merge from 1.0

--
[...truncated 2243 lines...]
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.167 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.locator.ReplicationStrategyEndpointCacheTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.52 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.SimpleStrategyTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.717 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.TokenMetadataTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.459 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceCounterTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 3.649 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceCounterTest):
 Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceCounterTest 
FAILED
[junit] Testsuite: 
org.apache.cassandra.service.AntiEntropyServiceStandardTest
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 3.701 sec
[junit] 
[junit] Testcase: 
testValidatorPrepare(org.apache.cassandra.service.AntiEntropyServiceStandardTest):
Caused an ERROR
[junit] /127.0.0.1:7010 is in use by another process.  Change 
listen_address:storage_port in cassandra.yaml to values that do not conflict 
with other services
[junit] org.apache.cassandra.config.ConfigurationException: /127.0.0.1:7010 
is in use by another process.  Change listen_address:storage_port in 
cassandra.yaml to values that do not conflict with other services
[junit] at 
org.apache.cassandra.net.MessagingService.getServerSocket(MessagingService.java:271)
[junit] at 
org.apache.cassandra.net.MessagingService.listen(MessagingService.java:241)
[junit] at 
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:484)
[junit] at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:461)
[junit] at 
org.apache.cassandra.service.AntiEntropyServiceTestAbstract.prepare(AntiEntropyServiceTestAbstract.java:80)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.AntiEntropyServiceStandardTest 
FAILED
[junit] Testsuite: org.apache.cassandra.service.CassandraServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.466 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.service.ConsistencyLevelTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.912 sec
[junit] 
[junit] Testcase: 
testReadWriteConsistencyChecks(org.apache.cassandra.service.ConsistencyLevelTest):
Caused an ERROR
[junit] invalid consistency level: ANY
[junit] java.lang.UnsupportedOperationException: invalid consistency level: 
ANY
[junit] at 
org.apache.cassandra.service.ReadCallback.determineBlockFor(ReadCallback.java:195)
[junit] at 
org.apache.cassandra.service.ReadCallback.(ReadCallback.java:68)
[junit] at 
org.apache.cassandra.service.StorageProxy.getReadCallback(StorageProxy.java:798)
[junit] at 
org.apache.cassandra.service.ConsistencyLevelTest.testReadWriteConsistencyChecks(ConsistencyLevelTest.java:110)
[junit] 
[junit] 
[junit] Test org.apache.cassandra.service.ConsistencyLevelTest FAILED
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Testsuite: org.apache.cassandra.service.EmbeddedCassandraServiceTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] 
[junit] Testcase: 
org.apache.cassandra.service.EmbeddedCassandraServiceTest:BeforeFirstTest:  
  Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the 
report does not reflect the time until the VM exit.
[junit] junit.f

How is Cassandra being used?

[Jonathan Ellis]

I started a "users survey" thread over on the users list (replies are
still trickling in), but as useful as that is, I'd like to get
feedback that is more quantitative and with a broader base.  This will
let us prioritize our development efforts to better address what
people are actually using it for, with less guesswork.  For instance:
we put a lot of effort into compression for 1.0.0; if it turned out
that only 1% of 1.0.x users actually enable compression, then it means
that we should spend less effort fine-tuning that moving forward, and
use the energy elsewhere.

(Of course it could also mean that we did a terrible job getting the
word out about new features and explaining how to use them, but either
way, it would be good to know!)

I propose adding a basic cluster reporting feature to cassandra.yaml,
enabled by default.  It would send anonymous information about your
cluster to an apache.org VM.  Information like, number (but not names)
of keyspaces and columnfamilies, ks-level options like compression, cf
options like compaction strategy, data types (again, not names) of
columns, average row size (or better: the histogram data), and average
sstables per read.

Thoughts?

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: How is Cassandra being used?

[Eric Evans]

On Tue, Nov 15, 2011 at 11:23 PM, Jonathan Ellis  wrote:
> I started a "users survey" thread over on the users list (replies are
> still trickling in), but as useful as that is, I'd like to get
> feedback that is more quantitative and with a broader base.  This will
> let us prioritize our development efforts to better address what
> people are actually using it for, with less guesswork.  For instance:
> we put a lot of effort into compression for 1.0.0; if it turned out
> that only 1% of 1.0.x users actually enable compression, then it means
> that we should spend less effort fine-tuning that moving forward, and
> use the energy elsewhere.
>
> (Of course it could also mean that we did a terrible job getting the
> word out about new features and explaining how to use them, but either
> way, it would be good to know!)
>
> I propose adding a basic cluster reporting feature to cassandra.yaml,
> enabled by default.  It would send anonymous information about your
> cluster to an apache.org VM.  Information like, number (but not names)
> of keyspaces and columnfamilies, ks-level options like compression, cf
> options like compaction strategy, data types (again, not names) of
> columns, average row size (or better: the histogram data), and average
> sstables per read.
>
> Thoughts?

I think this is potentially quite dangerous; There are a lot people
who get very twitchy at the idea of software that Phones Home.  I've
seen this so many times, and in all cases it was for software a lot
less sensitive than a database.

I'm sure you've already considered this though, you're already talking
about anonymity, and transparency, and what I assume is neutrality of
the collection endpoint (can apache actually provide a VM; is that a
thing?).  I'm just afraid that we'll scare people off before they can
be properly convinced that it's all on the up-and-up.

I'm curious to see what others think, but at the moment I'm hovering
somewhere around a -0 if it were opt-in (off by default).

-- 
Eric Evans
Acunu | http://www.acunu.com | @acunu

Jenkins build is unstable: Cassandra-Coverage #167

[Apache Jenkins Server]

See 

Re: How is Cassandra being used?

[Jonathan Ellis]

On Tue, Nov 15, 2011 at 7:02 PM, Eric Evans  wrote:
> I think this is potentially quite dangerous; There are a lot people
> who get very twitchy at the idea of software that Phones Home.  I've
> seen this so many times, and in all cases it was for software a lot
> less sensitive than a database.

True, but unlike most Home Phoners, ours will be out there in the open
and you can see exactly what it's sending (or not, if you disable it).
 I'm sure there's other examples in the wild of this, but the only one
I can think of is popcorn [1].

More broadly, my sense is that people are getting used to the idea
that it's okay to give away anonymous statistics as part of the price
of "free," although YMMclearlyV. I am, after all, a Windows user. :)

> I'm sure you've already considered this though, you're already talking
> about anonymity, and transparency, and what I assume is neutrality of
> the collection endpoint (can apache actually provide a VM; is that a
> thing?).

Yes, they provide Ubuntu or FreeBSD VMs.

> I'm just afraid that we'll scare people off before they can
> be properly convinced that it's all on the up-and-up.

How would you propose addressing this?

> I'm curious to see what others think, but at the moment I'm hovering
> somewhere around a -0 if it were opt-in (off by default).

I'm okay with opt-in if you think that's useful as a first step to
ease the twitchiness you mention, but longer term I think it's only
really useful if it's on by default. There's a lot of research that
shows that people tend to stick with whatever is the path of least
resistance [2], and specifically, my experience with Cassandra users
is exactly that -- one reason we've spent so much effort getting
defaults so good is because almost nobody goes beyond that.

[1] http://popcon.debian.org/
[2] 
http://www.richmondfed.org/publications/research/region_focus/2007/winter/pdf/feature2.pdf

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Updated http://wiki.apache.org/cassandra/ThriftExamples for 1.0.0

[Dave Brosius]

I've updated the thrift examples for Java found at

http://wiki.apache.org/cassandra/ThriftExamples

for version 1.0.0 and above, as the api has changed from what was 
presented there.


Hopefully i haven't foobared anything in the sample.

Re: How is Cassandra being used?

[Dave Brosius]

On 11/15/2011 09:01 PM, Jonathan Ellis wrote:

On Tue, Nov 15, 2011 at 7:02 PM, Eric Evans  wrote:

I think this is potentially quite dangerous; There are a lot people
who get very twitchy at the idea of software that Phones Home.  I've
seen this so many times, and in all cases it was for software a lot
less sensitive than a database.

True, but unlike most Home Phoners, ours will be out there in the open
and you can see exactly what it's sending (or not, if you disable it).
  I'm sure there's other examples in the wild of this, but the only one
I can think of is popcorn [1].

More broadly, my sense is that people are getting used to the idea
that it's okay to give away anonymous statistics as part of the price
of "free," although YMMclearlyV. I am, after all, a Windows user. :)


I'm sure you've already considered this though, you're already talking
about anonymity, and transparency, and what I assume is neutrality of
the collection endpoint (can apache actually provide a VM; is that a
thing?).

Yes, they provide Ubuntu or FreeBSD VMs.


  I'm just afraid that we'll scare people off before they can
be properly convinced that it's all on the up-and-up.

How would you propose addressing this?


I'm curious to see what others think, but at the moment I'm hovering
somewhere around a -0 if it were opt-in (off by default).

I'm okay with opt-in if you think that's useful as a first step to
ease the twitchiness you mention, but longer term I think it's only
really useful if it's on by default. There's a lot of research that
shows that people tend to stick with whatever is the path of least
resistance [2], and specifically, my experience with Cassandra users
is exactly that -- one reason we've spent so much effort getting
defaults so good is because almost nobody goes beyond that.

[1] http://popcon.debian.org/
[2] 
http://www.richmondfed.org/publications/research/region_focus/2007/winter/pdf/feature2.pdf



+1 for opt-in, altho perhaps you should think about how to increase 
opt-in rates. I'm afraid having it buried in the yaml will keep folks 
from enabling it, even if they were ok with doing so (if they knew it 
existed). Perhaps prompting (once) on server start up? -- not sure.

Re: How is Cassandra being used?

[Rick Shaw]

Speaking from the perspective of a large corporation with many and varied 
privacy and IP protection requirements it will be totally impossible to send 
ANY kind of data into the public network from a production Data Center. 

I expect most companies with similar concerns would want to be ASSURED that 
this could not happen by removing such code altogether. If you consider such 
code in the product you should make an easy way to configure it out completely 
not just disable it.

I don't think you will get enough valuable information for the heartache it 
will cause your internal corporate champions.

r.

On Nov 15, 2011, at 9:01 PM, Jonathan Ellis wrote:

> On Tue, Nov 15, 2011 at 7:02 PM, Eric Evans  wrote:
>> I think this is potentially quite dangerous; There are a lot people
>> who get very twitchy at the idea of software that Phones Home.  I've
>> seen this so many times, and in all cases it was for software a lot
>> less sensitive than a database.
> 
> True, but unlike most Home Phoners, ours will be out there in the open
> and you can see exactly what it's sending (or not, if you disable it).
> I'm sure there's other examples in the wild of this, but the only one
> I can think of is popcorn [1].
> 
> More broadly, my sense is that people are getting used to the idea
> that it's okay to give away anonymous statistics as part of the price
> of "free," although YMMclearlyV. I am, after all, a Windows user. :)
> 
>> I'm sure you've already considered this though, you're already talking
>> about anonymity, and transparency, and what I assume is neutrality of
>> the collection endpoint (can apache actually provide a VM; is that a
>> thing?).
> 
> Yes, they provide Ubuntu or FreeBSD VMs.
> 
>>  I'm just afraid that we'll scare people off before they can
>> be properly convinced that it's all on the up-and-up.
> 
> How would you propose addressing this?
> 
>> I'm curious to see what others think, but at the moment I'm hovering
>> somewhere around a -0 if it were opt-in (off by default).
> 
> I'm okay with opt-in if you think that's useful as a first step to
> ease the twitchiness you mention, but longer term I think it's only
> really useful if it's on by default. There's a lot of research that
> shows that people tend to stick with whatever is the path of least
> resistance [2], and specifically, my experience with Cassandra users
> is exactly that -- one reason we've spent so much effort getting
> defaults so good is because almost nobody goes beyond that.
> 
> [1] http://popcon.debian.org/
> [2] 
> http://www.richmondfed.org/publications/research/region_focus/2007/winter/pdf/feature2.pdf
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com

Re: How is Cassandra being used?

[Jonathan Ellis]

On Tue, Nov 15, 2011 at 10:02 PM, Rick Shaw  wrote:
> Speaking from the perspective of a large corporation with many and varied 
> privacy and IP protection requirements it will be totally impossible to send 
> ANY kind of data into the public network from a production Data Center.

At the risk of getting off-topic, wouldn't such corporations prevent
this the easy way, with a firewall?

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: How is Cassandra being used?

[Rick Shaw]

Yes of course. But then an alarm would sound, emails to management would be 
sent,  and the violator of the corporate policy would be hunted down and dealt 
with accordingly...

The point is that the responsible parties are expected to NOT do such things in 
the first place. I expect many shops are quite a bit less concerned with such 
things but I expect the larger and more exposed companies will just not want to 
opt in, and may need to prove to their betters that it is not only not enabled 
but the code has been actively removed or disabled.

I'm not trying to be a buzz-kill; I am  adding a parochial perspective.

r.

On Nov 15, 2011, at 11:09 PM, Jonathan Ellis wrote:

> On Tue, Nov 15, 2011 at 10:02 PM, Rick Shaw  wrote:
>> Speaking from the perspective of a large corporation with many and varied 
>> privacy and IP protection requirements it will be totally impossible to send 
>> ANY kind of data into the public network from a production Data Center.
> 
> At the risk of getting off-topic, wouldn't such corporations prevent
> this the easy way, with a firewall?
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com

Re: How is Cassandra being used?

[Radim Kolar]

ppl hate EHCache and Quartz for doing this.

Re: How is Cassandra being used?

[Jonathan Ellis]

I don't think the cases are parallel. Terracotta added this in (a) a
minor release, (b) without mentioning it in the release notes, and (c)
without a method to disable it.

On Tue, Nov 15, 2011 at 11:54 PM, Radim Kolar  wrote:
> ppl hate EHCache and Quartz for doing this.
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: How is Cassandra being used?

[Ashish]

On Wed, Nov 16, 2011 at 11:32 AM, Jonathan Ellis  wrote:
> I don't think the cases are parallel. Terracotta added this in (a) a
> minor release, (b) without mentioning it in the release notes, and (c)
> without a method to disable it.

for c) it can be disabled :)

Just curious, who owns this Phone home data - ASF?

thanks
ashish

Re: How is Cassandra being used?

[Norman Maurer]

2011/11/16 Jonathan Ellis :
> I started a "users survey" thread over on the users list (replies are
> still trickling in), but as useful as that is, I'd like to get
> feedback that is more quantitative and with a broader base.  This will
> let us prioritize our development efforts to better address what
> people are actually using it for, with less guesswork.  For instance:
> we put a lot of effort into compression for 1.0.0; if it turned out
> that only 1% of 1.0.x users actually enable compression, then it means
> that we should spend less effort fine-tuning that moving forward, and
> use the energy elsewhere.
>
> (Of course it could also mean that we did a terrible job getting the
> word out about new features and explaining how to use them, but either
> way, it would be good to know!)
>
> I propose adding a basic cluster reporting feature to cassandra.yaml,
> enabled by default.  It would send anonymous information about your
> cluster to an apache.org VM.  Information like, number (but not names)
> of keyspaces and columnfamilies, ks-level options like compression, cf
> options like compaction strategy, data types (again, not names) of
> columns, average row size (or better: the histogram data), and average
> sstables per read.
>
> Thoughts?

Hi there,

I'm not a cassandra dev but an user of it. I would really "hate" to
see such code in the cassandra code-base. I understand that it would
be kind of useful to get a better feeling about usage etc, but its
really something that scares the shit out of many managers (and even
devs ;) ).

So -1 to add this code (*non-binding)

Bye,
Norman