[jira] [Commented] (CASSANDRA-14790) LongBufferPoolTest burn test fails assertion

2018-10-15 Thread Dinesh Joshi (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651160#comment-16651160
 ] 

Dinesh Joshi commented on CASSANDRA-14790:
--

Hi [~jmeredithco], I left some comments on the PR (minor nits mostly). Also, 
could we fix the known races in the test?

> LongBufferPoolTest burn test fails assertion
> 
>
> Key: CASSANDRA-14790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14790
> Project: Cassandra
>  Issue Type: Test
>  Components: Testing
> Environment: Run under macOS 10.13.6, with patch (attached, but also 
> https://github.com/jonmeredith/cassandra/tree/failing-burn-test)
>Reporter: Jon Meredith
>Priority: Major
>  Labels: pull-request-available
> Attachments: 0001-Add-burn-testsome-target-to-build.xml.patch, 
> 0002-Initialize-before-running-LongBufferPoolTest.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The LongBufferPoolTest from the burn tests fails with an assertion error.  I 
> added a build target to run individual burn tests, and \{jasobrown} gave a 
> fix for the uninitialized test setup (attached), however the test now fails 
> on an assertion about recycling buffers.
> To reproduce (with patch applied)
> {{ant burn-testsome 
> -Dtest.name=org.apache.cassandra.utils.memory.LongBufferPoolTest 
> -Dtest.methods=testAllocate}}
> Output
> {{    [junit] Testcase: 
> testAllocate(org.apache.cassandra.utils.memory.LongBufferPoolTest): FAILED}}
> {{    [junit] null}}
> {{    [junit] junit.framework.AssertionFailedError}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Debug.check(BufferPool.java:204)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.assertAllRecycled(BufferPool.java:181)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate(LongBufferPoolTest.java:350)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate(LongBufferPoolTest.java:54)}}
> All major branches from 3.0 and later have issues, however the trunk branch 
> also warns about references not being released before the reference is 
> garbage collected.
> {{[junit] ERROR [Reference-Reaper:1] 2018-09-25 13:59:54,089 Ref.java:224 - 
> LEAK DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@7f58d19a) to @623704362 was 
> not released before the reference was garbage collected}}
> {{ [junit] ERROR [Reference-Reaper:1] 2018-09-25 13:59:54,089 Ref.java:255 - 
> Allocate trace org.apache.cassandra.utils.concurrent.Ref$State@7f58d19a:}}
> {{ [junit] Thread[pool-2-thread-24,5,main]}}
> {{ [junit] at java.lang.Thread.getStackTrace(Thread.java:1559)}}
> {{ [junit] at 
> org.apache.cassandra.utils.concurrent.Ref$Debug.(Ref.java:245)}}
> {{ [junit] at 
> org.apache.cassandra.utils.concurrent.Ref$State.(Ref.java:175)}}
> {{ [junit] at org.apache.cassandra.utils.concurrent.Ref.(Ref.java:97)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.setAttachment(BufferPool.java:663)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.get(BufferPool.java:803)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.get(BufferPool.java:793)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$LocalPool.get(BufferPool.java:388)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.maybeTakeFromPool(BufferPool.java:143)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.takeFromPool(BufferPool.java:115)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.get(BufferPool.java:85)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$3.allocate(LongBufferPoolTest.java:296)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$3.testOne(LongBufferPoolTest.java:246)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:399)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:379)}}
> {{ [junit] at java.util.concurrent.FutureTask.run(FutureTask.java:266)}}
> {{ [junit] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}}
> {{ [junit] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}}
> {{ [junit] at java.lang.Thread.run(Thread.java:748)}}
>  
> Perhaps the environment is not being set up correctly for the tests.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14825) Expose table schema for drivers

2018-10-15 Thread Chris Lohfink (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink updated CASSANDRA-14825:
--
Status: Patch Available  (was: Open)

> Expose table schema for drivers
> ---
>
> Key: CASSANDRA-14825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Chris Lohfink
>Assignee: Chris Lohfink
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the drivers recreate the CQL for the tables by putting together the 
> system table values. This is very difficult to keep up to date and buggy 
> enough that its only even supported in Java and Python drivers. Cassandra 
> already has some limited output available for snapshots that we could provide 
> in a virtual table or new query that the drivers can fetch. This can greatly 
> reduce the complexity of drivers while also reducing bugs like 
> CASSANDRA-14822 as the underlying schema and properties change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14825) Expose table schema for drivers

2018-10-15 Thread ASF GitHub Bot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated CASSANDRA-14825:
---
Labels: pull-request-available  (was: )

> Expose table schema for drivers
> ---
>
> Key: CASSANDRA-14825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Chris Lohfink
>Assignee: Chris Lohfink
>Priority: Major
>  Labels: pull-request-available
>
> Currently the drivers recreate the CQL for the tables by putting together the 
> system table values. This is very difficult to keep up to date and buggy 
> enough that its only even supported in Java and Python drivers. Cassandra 
> already has some limited output available for snapshots that we could provide 
> in a virtual table or new query that the drivers can fetch. This can greatly 
> reduce the complexity of drivers while also reducing bugs like 
> CASSANDRA-14822 as the underlying schema and properties change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog

2018-10-15 Thread Dinesh Joshi (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651138#comment-16651138
 ] 

Dinesh Joshi commented on CASSANDRA-14631:
--

[~zznate] any idea what is going on here?

> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
>  Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08 
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png, feed404.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is 
> about blog.
>  
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>  
> Please feel free to file a ticket (label: Documentation and Website).
>  
> It looks like Jekyll, the static site generator used to build the website, 
> has a plugin that generates Atom feeds if someone would like to work on 
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14820) Upgrade to 4.0 fails with NullPointerException

2018-10-15 Thread Dinesh Joshi (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Joshi updated CASSANDRA-14820:
-
Status: Ready to Commit  (was: Patch Available)

> Upgrade to 4.0 fails with NullPointerException
> --
>
> Key: CASSANDRA-14820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14820
> Project: Cassandra
>  Issue Type: Bug
>  Components: 4.0
>Reporter: Tommy Stendahl
>Assignee: Ariel Weisberg
>Priority: Major
>
> I tested to upgrade an existing cluster to latest 4.0 but it fails with a 
> NullPointerException, I upgraded from 3.0.15 but upgrading from any 3.0.x or 
> 3.11.x to 4.0 will give the same fault.
> {noformat}
>  
> 2018-10-12T11:27:02.261+0200 ERROR [main] CassandraDaemon.java:251 Error 
> while loading schema: 
> java.lang.NullPointerException: null
>  at org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:156)
>  at 
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:41)
>  at 
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:28)
>  at 
> org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:116)
>  at 
> org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:267)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.createTableParamsFromRow(SchemaKeyspace.java:997)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchTable(SchemaKeyspace.java:973)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchTables(SchemaKeyspace.java:927)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:886)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:877)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:865)
>  at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:102)
>  at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:91)
>  at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:247)
>  at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:590)
>  at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:679)
> {noformat}
>  The problem seams to be line 997 in SchemaKeyspace.java
>  
> {noformat}
> .speculativeWriteThreshold(SpeculativeRetryPolicy.fromString(row.getString("speculative_write_threshold"{noformat}
> speculative_write_threshold is a new table option introduced in 
> CASSANDRA-14404, when upgrading the table option is missing and we get a 
> NullPointerException on this line.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14820) Upgrade to 4.0 fails with NullPointerException

2018-10-15 Thread Dinesh Joshi (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651137#comment-16651137
 ] 

Dinesh Joshi commented on CASSANDRA-14820:
--

I found one minor issue in {{ddl.rst#L466}} - {{additional_write_policy}} 
description seems to be duplicated from the earlier row. Also minor nit on the 
white space. Please fix on commit. Thanks!

> Upgrade to 4.0 fails with NullPointerException
> --
>
> Key: CASSANDRA-14820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14820
> Project: Cassandra
>  Issue Type: Bug
>  Components: 4.0
>Reporter: Tommy Stendahl
>Assignee: Ariel Weisberg
>Priority: Major
>
> I tested to upgrade an existing cluster to latest 4.0 but it fails with a 
> NullPointerException, I upgraded from 3.0.15 but upgrading from any 3.0.x or 
> 3.11.x to 4.0 will give the same fault.
> {noformat}
>  
> 2018-10-12T11:27:02.261+0200 ERROR [main] CassandraDaemon.java:251 Error 
> while loading schema: 
> java.lang.NullPointerException: null
>  at org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:156)
>  at 
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:41)
>  at 
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:28)
>  at 
> org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:116)
>  at 
> org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:267)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.createTableParamsFromRow(SchemaKeyspace.java:997)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchTable(SchemaKeyspace.java:973)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchTables(SchemaKeyspace.java:927)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:886)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:877)
>  at 
> org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:865)
>  at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:102)
>  at org.apache.cassandra.schema.Schema.loadFromDisk(Schema.java:91)
>  at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:247)
>  at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:590)
>  at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:679)
> {noformat}
>  The problem seams to be line 997 in SchemaKeyspace.java
>  
> {noformat}
> .speculativeWriteThreshold(SpeculativeRetryPolicy.fromString(row.getString("speculative_write_threshold"{noformat}
> speculative_write_threshold is a new table option introduced in 
> CASSANDRA-14404, when upgrading the table option is missing and we get a 
> NullPointerException on this line.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14824) Expand range tombstone validation checks to multiple interim request stages

2018-10-15 Thread Blake Eggleston (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650961#comment-16650961
 ] 

Blake Eggleston commented on CASSANDRA-14824:
-

looks good to me. The only think I might change would be to move the MERGED 
validator out of queryStorage and into executeLocally, which would validate the 
pre-purge stage for 2i implementations that may not be checking, but I don't 
feel strongly about it.

> Expand range tombstone validation checks to multiple interim request stages
> ---
>
> Key: CASSANDRA-14824
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14824
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Major
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> {{RTBoundValidator}} was originally only added to verify the end-game 
> response iterator produced by {{ReadCommand}}.
> However, turns out it's possible for sequencing errors in lower-level 
> iterators to be silently erased by upstream iterators - as a result of 
> merging two invalid iterators into one valid iterator, for example. 
> CASSANDRA-14823 can create such a scenario.
> The upcoming patch would attach the checker at the intermediate stages, 
> ensuring that we can detect those otherwise silent corruptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

2018-10-15 Thread Blake Eggleston (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650833#comment-16650833
 ] 

Blake Eggleston commented on CASSANDRA-14823:
-

Changes look good to me. Pulled in, merged to 3.11 and started another run of 
tests:
|[3.0|https://github.com/bdeggleston/cassandra/tree/14823-3.0]|[circle|https://circleci.com/workflow-run/fd588958-4771-4d4e-8569-772415523c88]|
|[3.11|https://github.com/bdeggleston/cassandra/tree/14823-3.11]|[circle|https://circleci.com/workflow-run/37a12a6a-f2ab-4591-a5c7-83b926ba655a]|

> Legacy sstables with range tombstones spanning multiple index blocks create 
> invalid bound sequences on 3.0+
> ---
>
> Key: CASSANDRA-14823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14823
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> During upgrade from 2.1 to 3.0, reading old sstables in reverse order would 
> generate invalid sequences of range tombstone bounds if their range 
> tombstones spanned multiple column index blocks. The read fails in different 
> ways depending on whether the 2.1 tables were produced by a flush or a 
> compaction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14825) Expose table schema for drivers

2018-10-15 Thread Chris Lohfink (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink reassigned CASSANDRA-14825:
-

Assignee: Chris Lohfink

> Expose table schema for drivers
> ---
>
> Key: CASSANDRA-14825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Chris Lohfink
>Assignee: Chris Lohfink
>Priority: Major
>
> Currently the drivers recreate the CQL for the tables by putting together the 
> system table values. This is very difficult to keep up to date and buggy 
> enough that its only even supported in Java and Python drivers. Cassandra 
> already has some limited output available for snapshots that we could provide 
> in a virtual table or new query that the drivers can fetch. This can greatly 
> reduce the complexity of drivers while also reducing bugs like 
> CASSANDRA-14822 as the underlying schema and properties change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-14825) Expose table schema for drivers

2018-10-15 Thread Chris Lohfink (JIRA) 
Chris Lohfink created CASSANDRA-14825:
-

 Summary: Expose table schema for drivers
 Key: CASSANDRA-14825
 URL: https://issues.apache.org/jira/browse/CASSANDRA-14825
 Project: Cassandra
  Issue Type: Improvement
Reporter: Chris Lohfink


Currently the drivers recreate the CQL for the tables by putting together the 
system table values. This is very difficult to keep up to date and buggy enough 
that its only even supported in Java and Python drivers. Cassandra already has 
some limited output available for snapshots that we could provide in a virtual 
table or new query that the drivers can fetch. This can greatly reduce the 
complexity of drivers while also reducing bugs like CASSANDRA-14822 as the 
underlying schema and properties change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14824) Expand range tombstone validation checks to multiple interim request stages

2018-10-15 Thread Aleksey Yeschenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-14824:
--
Status: Patch Available  (was: Open)

> Expand range tombstone validation checks to multiple interim request stages
> ---
>
> Key: CASSANDRA-14824
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14824
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Major
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> {{RTBoundValidator}} was originally only added to verify the end-game 
> response iterator produced by {{ReadCommand}}.
> However, turns out it's possible for sequencing errors in lower-level 
> iterators to be silently erased by upstream iterators - as a result of 
> merging two invalid iterators into one valid iterator, for example. 
> CASSANDRA-14823 can create such a scenario.
> The upcoming patch would attach the checker at the intermediate stages, 
> ensuring that we can detect those otherwise silent corruptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14824) Expand range tombstone validation checks to multiple interim request stages

2018-10-15 Thread Aleksey Yeschenko (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650661#comment-16650661
 ] 

Aleksey Yeschenko commented on CASSANDRA-14824:
---

Code for [3.0|https://github.com/iamaleksey/cassandra/commits/14824-3.0], CI 
for 
[3.0|https://circleci.com/workflow-run/7cd1b687-dabd-4c02-b70b-3ca908471043]; 
Some hiccups with 3.11 and 4.0 branches, will resolve soonish.

> Expand range tombstone validation checks to multiple interim request stages
> ---
>
> Key: CASSANDRA-14824
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14824
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Major
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> {{RTBoundValidator}} was originally only added to verify the end-game 
> response iterator produced by {{ReadCommand}}.
> However, turns out it's possible for sequencing errors in lower-level 
> iterators to be silently erased by upstream iterators - as a result of 
> merging two invalid iterators into one valid iterator, for example. 
> CASSANDRA-14823 can create such a scenario.
> The upcoming patch would attach the checker at the intermediate stages, 
> ensuring that we can detect those otherwise silent corruptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14824) Expand range tombstone validation checks to multiple interim request stages

2018-10-15 Thread Aleksey Yeschenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-14824:
--
Reviewers: Blake Eggleston, Sam Tunnicliffe
 Reviewer:   (was: Sam Tunnicliffe)

> Expand range tombstone validation checks to multiple interim request stages
> ---
>
> Key: CASSANDRA-14824
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14824
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Major
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> {{RTBoundValidator}} was originally only added to verify the end-game 
> response iterator produced by {{ReadCommand}}.
> However, turns out it's possible for sequencing errors in lower-level 
> iterators to be silently erased by upstream iterators - as a result of 
> merging two invalid iterators into one valid iterator, for example. 
> CASSANDRA-14823 can create such a scenario.
> The upcoming patch would attach the checker at the intermediate stages, 
> ensuring that we can detect those otherwise silent corruptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-14824) Expand range tombstone validation checks to multiple interim request stages

2018-10-15 Thread Aleksey Yeschenko (JIRA) 
Aleksey Yeschenko created CASSANDRA-14824:
-

 Summary: Expand range tombstone validation checks to multiple 
interim request stages
 Key: CASSANDRA-14824
 URL: https://issues.apache.org/jira/browse/CASSANDRA-14824
 Project: Cassandra
  Issue Type: Improvement
Reporter: Aleksey Yeschenko
Assignee: Aleksey Yeschenko
 Fix For: 3.0.x, 3.11.x, 4.0.x


{{RTBoundValidator}} was originally only added to verify the end-game response 
iterator produced by {{ReadCommand}}.

However, turns out it's possible for sequencing errors in lower-level iterators 
to be silently erased by upstream iterators - as a result of merging two 
invalid iterators into one valid iterator, for example. CASSANDRA-14823 can 
create such a scenario.

The upcoming patch would attach the checker at the intermediate stages, 
ensuring that we can detect those otherwise silent corruptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

2018-10-15 Thread Sam Tunnicliffe (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650286#comment-16650286
 ] 

Sam Tunnicliffe commented on CASSANDRA-14823:
-

I realised that I'd overlooked one additional aspect here: that a 2.1 has the 
potential to have multiple repeated RTs following a block boundary. So I've 
updated the test data generator to do that, though I could only figure out how 
to do it via the compaction path. While I was at it, I changed the naming of 
the test tables slightly from {{...\_compact\_...}} to {{...\_compacted\_...}} 
to avoid potential confusion due to the existing test tables named that way to 
indicate that they use {{COMPACT STORAGE}}. 
[3.0 branch|https://github.com/beobal/cassandra/tree/14823-3.0]
[2.1 sstable 
generator|https://github.com/beobal/cassandra/commit/420457c3192952206e07276be7c2edf86aa79a7e]
[circle|https://circleci.com/gh/beobal/workflows/cassandra/tree/cci%2F14823-3.0]


> Legacy sstables with range tombstones spanning multiple index blocks create 
> invalid bound sequences on 3.0+
> ---
>
> Key: CASSANDRA-14823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14823
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> During upgrade from 2.1 to 3.0, reading old sstables in reverse order would 
> generate invalid sequences of range tombstone bounds if their range 
> tombstones spanned multiple column index blocks. The read fails in different 
> ways depending on whether the 2.1 tables were produced by a flush or a 
> compaction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13487) Generate snapshot packages through Jenkins

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-13487:
---
Attachment: 13487-v2.patch

> Generate snapshot packages through Jenkins
> --
>
> Key: CASSANDRA-13487
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13487
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Build
>Reporter: Stefan Podkowinski
>Priority: Major
> Attachments: 13487-v2.patch, 13487.patch
>
>
> Creating packages through the new docker based build scripts now work pretty 
> much independent from any local environment, as long as docker is available, 
> e.g. also on Jenkins. Having daily snapshots available for deb/rpm artifacts 
> would enable us to provide users dev-releases for testing and validating 
> fixes.
> I've created a branch for the Jenkins integration, which can be found here:
> https://github.com/spodkowinski/cassandra-builds/tree/jenkins_debrpm
> The major issue I'm currently struggling with is the handling of the actual 
> version value. We need to find a way to have Jenkins recognize the correct 
> version for the branch being build. Also we must create $version-SNAPSHOT 
> packages, as builds are not official releases and we should not have any 
> packages for versions that aren't published yet.
> The Debian build process will use the version defined in 
> {{debian/changelog}}. Adding a -SNAPSHOT suffix for the version should work, 
> but this has to be handled manually and care must be taken to change the 
> value back again for a regular release.
> With RPMs, the version must be set for {{cassandra.spec}}, which is currently 
> done by running {noformat}rpmbuild --define="version ${CASSANDRA_VERSION}" 
> -ba ./redhat/cassandra.spec{noformat}, where the version is passed as a 
> parameter by {{build-scripts/cassandra-rpm-packaging.sh}}. Maybe we could 
> grep the version from build.xml here?
> So I wonder if there any way we can keep track of the version in a single 
> place, such as build.xml or CHANGES. Afterwards we also need to enable a 
> SNAPSHOT mode, maybe by setting a Jenkins environment value.
> /cc [~mshuler]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13487) Generate snapshot packages through Jenkins

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-13487:
---
Attachment: 13487.patch

> Generate snapshot packages through Jenkins
> --
>
> Key: CASSANDRA-13487
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13487
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Build
>Reporter: Stefan Podkowinski
>Priority: Major
> Attachments: 13487.patch
>
>
> Creating packages through the new docker based build scripts now work pretty 
> much independent from any local environment, as long as docker is available, 
> e.g. also on Jenkins. Having daily snapshots available for deb/rpm artifacts 
> would enable us to provide users dev-releases for testing and validating 
> fixes.
> I've created a branch for the Jenkins integration, which can be found here:
> https://github.com/spodkowinski/cassandra-builds/tree/jenkins_debrpm
> The major issue I'm currently struggling with is the handling of the actual 
> version value. We need to find a way to have Jenkins recognize the correct 
> version for the branch being build. Also we must create $version-SNAPSHOT 
> packages, as builds are not official releases and we should not have any 
> packages for versions that aren't published yet.
> The Debian build process will use the version defined in 
> {{debian/changelog}}. Adding a -SNAPSHOT suffix for the version should work, 
> but this has to be handled manually and care must be taken to change the 
> value back again for a regular release.
> With RPMs, the version must be set for {{cassandra.spec}}, which is currently 
> done by running {noformat}rpmbuild --define="version ${CASSANDRA_VERSION}" 
> -ba ./redhat/cassandra.spec{noformat}, where the version is passed as a 
> parameter by {{build-scripts/cassandra-rpm-packaging.sh}}. Maybe we could 
> grep the version from build.xml here?
> So I wonder if there any way we can keep track of the version in a single 
> place, such as build.xml or CHANGES. Afterwards we also need to enable a 
> SNAPSHOT mode, maybe by setting a Jenkins environment value.
> /cc [~mshuler]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

2018-10-15 Thread Aleksey Yeschenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-14823:
--
Reviewers: Aleksey Yeschenko, Sam Tunnicliffe
 Reviewer:   (was: Sam Tunnicliffe)

> Legacy sstables with range tombstones spanning multiple index blocks create 
> invalid bound sequences on 3.0+
> ---
>
> Key: CASSANDRA-14823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14823
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> During upgrade from 2.1 to 3.0, reading old sstables in reverse order would 
> generate invalid sequences of range tombstone bounds if their range 
> tombstones spanned multiple column index blocks. The read fails in different 
> ways depending on whether the 2.1 tables were produced by a flush or a 
> compaction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14228) Add expiration date overflow notice and recovery instructions to doc

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski reassigned CASSANDRA-14228:
--

Assignee: Andrew Baker

> Add expiration date overflow notice and recovery instructions to doc
> 
>
> Key: CASSANDRA-14228
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14228
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation and Website
>Reporter: Paulo Motta
>Assignee: Andrew Baker
>Priority: Minor
>  Labels: lhf
>
> On CASSANDRA-14092 we added a new 
> [CASSANDRA-14092.txt|https://github.com/apache/cassandra/blob/trunk/CASSANDRA-14092.txt]
>  file with the maximum ttl expiration notice and recovery instructions for 
> affected users.
> We should probably also add the contents of this file to the documentation 
> with some basic formatting.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

cassandra git commit: Docs: update patch acceptance policies for existing branches

2018-10-15 Thread spod 
Repository: cassandra
Updated Branches:
  refs/heads/trunk 2adf5d1df -> e82ecf87a


Docs: update patch acceptance policies for existing branches


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e82ecf87
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e82ecf87
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e82ecf87

Branch: refs/heads/trunk
Commit: e82ecf87a1d093504a763d211a30d5a252fd3a1b
Parents: 2adf5d1
Author: Stefan Podkowinski 
Authored: Mon Oct 15 13:17:33 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 13:19:06 2018 +0200

--
 doc/source/development/patches.rst | 20 ++--
 1 file changed, 14 insertions(+), 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e82ecf87/doc/source/development/patches.rst
--
diff --git a/doc/source/development/patches.rst 
b/doc/source/development/patches.rst
index 3bab5d0..e8e50f6 100644
--- a/doc/source/development/patches.rst
+++ b/doc/source/development/patches.rst
@@ -62,18 +62,26 @@ There are currently multiple Cassandra versions maintained 
in individual branche
 === ==
 Version Policy
 === ==
-3.x Tick-tock (see below)
-3.0 Bug fixes only
-2.2 Bug fixes only
+4.0 Code freeze (see below)
+3.11Critical bug fixes only
+3.0 Critical bug fixes only
+2.2 Critical bug fixes only
 2.1 Critical bug fixes only
 === ==
 
 Corresponding branches in git are easy to recognize as they are named 
``cassandra-`` (e.g. ``cassandra-3.0``). The ``trunk`` branch is an 
exception, as it contains the most recent commits from all other branches and 
is used for creating new branches for future tick-tock releases.
 
-Tick-Tock Releases
-""
+4.0 Code Freeze
+"""
 
-New releases created as part of the `tick-tock release process 
`_ will 
either focus on stability (odd version numbers) or introduce new features (even 
version numbers). Any code for new Cassandra features you should be based on 
the latest, unreleased 3.x branch with even version number or based on trunk.
+Patches for new features are currently not accepted for 4.0 or any earlier 
versions. Starting with the code freeze in September, all efforts should focus 
on stabilizing the 4.0 branch before the first official release. During that 
time, only the following patches will be considered for acceptance:
+
+ * Bug fixes
+ * Measurable performance improvements
+ * Changes not distributed as part of the release such as:
+ * Testing related improvements and fixes
+ * Build and infrastructure related changes
+ * Documentation
 
 Bug Fixes
 "


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14810) Upgrade dtests to pytest-3.8

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-14810:
---
Reviewer: Stefan Podkowinski
  Status: Patch Available  (was: Open)

> Upgrade dtests to pytest-3.8
> 
>
> Key: CASSANDRA-14810
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14810
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Stefan Podkowinski
>Assignee: Thomas Pouget-Abadie
>Priority: Minor
>  Labels: lhf
> Attachments: 14810-master.txt
>
>
> The [dtest project|https://github.com/apache/cassandra-dtest] uses pytest as 
> test runner of choice for executing tests on builds.apache.org or CircleCI. 
> The pytest dependency has recently been upgrade to 3.6, but couldn't be 
> upgrade to the most recent 3.8 version, due to issues described below.
> Before test execution, the {{run_dtests.py}} script will gather a list of all 
> tests:
>  {{./run_dtests.py --dtest-print-tests-only}}
> Afterwards pytest can be started with any of the output lines as argument. 
> With pytest-3.8 however, the output format changed and preventing pytest to 
> find the test:
>  {{pytest 
> upgrade_tests/upgrade_supercolumns_test.py::TestSCUpgrade::test_upgrade_super_columns_through_limited_versions}}
>  vs
>  {{pytest 
> upgrade_supercolumns_test.py::TestSCUpgrade::test_upgrade_super_columns_through_limited_versions}}
> The underlying issue appears to be the changes in the {{pytest 
> --collect-only}} output, consumed in {{run_dtests.py}}, which now includes a 
>  element that needs to be parsed as well to derive at the path as we 
> did before. We'd have to parse the new output and assemble the correct paths 
> again, so we can use run_dtests.py as we did before with pytest 3.6.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14690) Add dtests for fqltool replay/compare

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-14690:
---
Reviewer: Stefan Podkowinski

> Add dtests for fqltool replay/compare
> -
>
> Key: CASSANDRA-14690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14690
> Project: Cassandra
>  Issue Type: Test
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Major
>  Labels: fqltool
>
> We should add some basic round-trip dtests for {{fqltool replay}} and 
> {{compare}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14806) CircleCI workflow improvements and Java 11 support

2018-10-15 Thread Marcus Eriksson (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Eriksson updated CASSANDRA-14806:

Reviewer: Marcus Eriksson

> CircleCI workflow improvements and Java 11 support
> --
>
> Key: CASSANDRA-14806
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14806
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Testing
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>Priority: Major
>
> The current CircleCI config could use some cleanup and improvements. First of 
> all, the config has been made more modular by using the new CircleCI 2.1 
> executors and command elements. Based on CASSANDRA-14713, there's now also a 
> Java 11 executor that will allow running tests under Java 11. The {{build}} 
> step will be done using Java 11 in all cases, so we can catch any regressions 
> for that and also test the Java 11 multi-jar artifact during dtests, that 
> we'd also create during the release process.
> The job workflow has now also been changed to make use of the [manual job 
> approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
>  feature, which now allows running dtest jobs only on request and not 
> automatically with every commit. The Java8 unit tests still do, but that 
> could also be easily changed if needed. See [example 
> workflow|https://circleci.com/workflow-run/be25579d-3cbb-4258-9e19-b1f571873850]
>  with start_ jobs being triggers needed manual approval for starting the 
> actual jobs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14806) CircleCI workflow improvements and Java 11 support

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-14806:
---
Description: 
The current CircleCI config could use some cleanup and improvements. First of 
all, the config has been made more modular by using the new CircleCI 2.1 
executors and command elements. Based on CASSANDRA-14713, there's now also a 
Java 11 executor that will allow running tests under Java 11. The {{build}} 
step will be done using Java 11 in all cases, so we can catch any regressions 
for that and also test the Java 11 multi-jar artifact during dtests, that we'd 
also create during the release process.

The job workflow has now also been changed to make use of the [manual job 
approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
 feature, which now allows running dtest jobs only on request and not 
automatically with every commit. The Java8 unit tests still do, but that could 
also be easily changed if needed. See [example 
workflow|https://circleci.com/workflow-run/be25579d-3cbb-4258-9e19-b1f571873850]
 with start_ jobs being triggers needed manual approval for starting the actual 
jobs.

  was:
The current CircleCI config could use some cleanup and improvements. First of 
all, the config has been made more modular by using the new CircleCI 2.1 
executors and command elements. Based on CASSANDRA-14713, there's now also a 
Java 11 executor that will allow running tests under Java 11. The {{build}} 
step will be done using Java 11 in all cases, so we can catch any regressions 
for that and also test the Java 11 multi-jar artifact during dtests, that we'd 
also create during the release process.

The job workflow has now also been changed to make use of the [manual job 
approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
 feature, which now allows running dtest jobs only on request and not 
automatically with every commit. The Java8 unit tests still do, but that could 
also be easily changed if needed. See [example 
workflow|https://circleci.com/workflow-run/08ecb879-9aaa-4d75-84d6-b00dc9628425]
 with start_ jobs being triggers needed manual approval for starting the actual 
jobs.

There was some churn in manually editing the config for paid and non-paid 
resource tiers before. This has been mostly mitigated now by using project 
settings instead, for overriding lower defaults (see below) and scheduling 
dtests on request, which will only run on paid accounts nonetheless, so we use 
high settings for these right away. The only issue left is the question how we 
may be able to dynamically adjust the {{resource_class}} and {{parallelism}} 
settings for unit tests. So at this point, the CircleCI config will work for 
both paid and non-paid by default, but paid accounts will see slower unit test 
results, as only medium instances are used (ie. 15min instead of 4min).

Attention CircleCI paid account users: you'll have to add "{{CCM_MAX_HEAP_SIZE: 
2048M}}" and "{{CCM_HEAP_NEWSIZE: 512M}}" to your project's environment 
settings or create a context, to override the lower defaults for free instances!


> CircleCI workflow improvements and Java 11 support
> --
>
> Key: CASSANDRA-14806
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14806
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Testing
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>Priority: Major
>
> The current CircleCI config could use some cleanup and improvements. First of 
> all, the config has been made more modular by using the new CircleCI 2.1 
> executors and command elements. Based on CASSANDRA-14713, there's now also a 
> Java 11 executor that will allow running tests under Java 11. The {{build}} 
> step will be done using Java 11 in all cases, so we can catch any regressions 
> for that and also test the Java 11 multi-jar artifact during dtests, that 
> we'd also create during the release process.
> The job workflow has now also been changed to make use of the [manual job 
> approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
>  feature, which now allows running dtest jobs only on request and not 
> automatically with every commit. The Java8 unit tests still do, but that 
> could also be easily changed if needed. See [example 
> workflow|https://circleci.com/workflow-run/be25579d-3cbb-4258-9e19-b1f571873850]
>  with start_ jobs being triggers needed manual approval for starting the 
> actual jobs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional

[jira] [Commented] (CASSANDRA-14806) CircleCI workflow improvements and Java 11 support

2018-10-15 Thread Stefan Podkowinski (JIRA) 


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649871#comment-16649871
 ] 

Stefan Podkowinski commented on CASSANDRA-14806:


I've now basically rewritten the CircleCI config to make heavily use of 
parameters to avoid redundant copy and pasting of script snippets. Combined 
with job approvals, we can now have a broader selection of tests. So far I've 
added: ant long-test, test-burn, cql-test, test-compression, stress-test, 
fqltool-test. Cqlsh dtests will be added in CASSANDRA-14298.

Unfortunately I wasn't able to solve the requirement for not having to manually 
edit the config for switching between high/free resource settings. CircleCI 
support was so kind to look at the issue and latest config, but wasn't able to 
advise a solution either. So I guess we still have to live with that situation 
for a while.

 

> CircleCI workflow improvements and Java 11 support
> --
>
> Key: CASSANDRA-14806
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14806
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Testing
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>Priority: Major
>
> The current CircleCI config could use some cleanup and improvements. First of 
> all, the config has been made more modular by using the new CircleCI 2.1 
> executors and command elements. Based on CASSANDRA-14713, there's now also a 
> Java 11 executor that will allow running tests under Java 11. The {{build}} 
> step will be done using Java 11 in all cases, so we can catch any regressions 
> for that and also test the Java 11 multi-jar artifact during dtests, that 
> we'd also create during the release process.
> The job workflow has now also been changed to make use of the [manual job 
> approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
>  feature, which now allows running dtest jobs only on request and not 
> automatically with every commit. The Java8 unit tests still do, but that 
> could also be easily changed if needed. See [example 
> workflow|https://circleci.com/workflow-run/08ecb879-9aaa-4d75-84d6-b00dc9628425]
>  with start_ jobs being triggers needed manual approval for starting the 
> actual jobs.
> There was some churn in manually editing the config for paid and non-paid 
> resource tiers before. This has been mostly mitigated now by using project 
> settings instead, for overriding lower defaults (see below) and scheduling 
> dtests on request, which will only run on paid accounts nonetheless, so we 
> use high settings for these right away. The only issue left is the question 
> how we may be able to dynamically adjust the {{resource_class}} and 
> {{parallelism}} settings for unit tests. So at this point, the CircleCI 
> config will work for both paid and non-paid by default, but paid accounts 
> will see slower unit test results, as only medium instances are used (ie. 
> 15min instead of 4min).
> Attention CircleCI paid account users: you'll have to add 
> "{{CCM_MAX_HEAP_SIZE: 2048M}}" and "{{CCM_HEAP_NEWSIZE: 512M}}" to your 
> project's environment settings or create a context, to override the lower 
> defaults for free instances!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14713) Update docker image used for testing

2018-10-15 Thread Stefan Podkowinski (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-14713:
---
   Resolution: Fixed
Fix Version/s: 4.0
   3.11.4
   3.0.18
   2.2.14
   Status: Resolved  (was: Ready to Commit)

I haven't noticed any regressions from the dtest updates so far. Looks like we 
can take the final step switching to the new docker image as well.

CircleCI config update committed as dcd92a9 and merged upwards.

> Update docker image used for testing
> 
>
> Key: CASSANDRA-14713
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14713
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>Priority: Major
> Fix For: 2.2.14, 3.0.18, 3.11.4, 4.0
>
> Attachments: Dockerfile
>
>
> Tests executed on builds.apache.org ({{docker/jenkins/jenkinscommand.sh}}) 
> and circleCI ({{.circleci/config.yml}}) will currently use the same 
> [cassandra-test|https://hub.docker.com/r/kjellman/cassandra-test/] docker 
> image ([github|https://github.com/mkjellman/cassandra-test-docker]) by 
> [~mkjellman].
> We should manage this image on our own as part of cassandra-builds, to keep 
> it updated. There's also a [Apache 
> user|https://hub.docker.com/u/apache/?page=1] on docker hub for publishing 
> images.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[05/10] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

2018-10-15 Thread spod 
Merge branch 'cassandra-2.2' into cassandra-3.0


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/300fff27
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/300fff27
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/300fff27

Branch: refs/heads/cassandra-3.11
Commit: 300fff2722ddf2019b428ea0f924aae2eed56016
Parents: ab0e30e dcd92a9
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:41:22 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:41:59 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/300fff27/.circleci/config.yml
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[04/10] cassandra git commit: Use new docker image for CircleCI builds

2018-10-15 Thread spod 
Use new docker image for CircleCI builds

patch by Stefan Podkowinski; reviewed by Marcus Eriksson for CASSANDRA-14713


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dcd92a93
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dcd92a93
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dcd92a93

Branch: refs/heads/trunk
Commit: dcd92a93ab12c08963bae8a83340bf7fdfe186dd
Parents: 62e48c5
Author: Stefan Podkowinski 
Authored: Tue Oct 9 14:12:54 2018 +0200
Committer: Stefan Podkowinski 
Committed: Tue Oct 9 14:12:54 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dcd92a93/.circleci/config.yml
--
diff --git a/.circleci/config.yml b/.circleci/config.yml
index f881b70..c389cbc 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -1,10 +1,10 @@
 default_env_vars: _env_vars
-JAVA_HOME: /usr/local/openjdk8u154-cassandra-b02
-ANT_HOME: /usr/local/apache-ant-1.10.1
+JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ANT_HOME: /usr/share/ant
 LANG: en_US.UTF-8
-JDK_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA8_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA7_HOME: /usr/local/openjdk7u82-cassandra-b02
+JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA11_HOME: /usr/lib/jvm/java-11-openjdk-amd64
 KEEP_TEST_DIR: true
 DEFAULT_DIR: /home/cassandra/cassandra-dtest
 PYTHONIOENCODING: utf-8
@@ -68,7 +68,7 @@ workflows:
 build_and_run_tests: *default_jobs
 #build_and_run_tests: *with_dtest_jobs_only
 #build_and_run_tests: *with_dtest_jobs
-docker_image: _image kjellman/cassandra-test:0.4.3
+docker_image: _image spod/cassandra-testing-ubuntu18-java11
 version: 2
 jobs:
   build:
@@ -211,7 +211,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run
@@ -289,7 +289,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[10/10] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

2018-10-15 Thread spod 
Merge branch 'cassandra-3.11' into trunk


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2adf5d1d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2adf5d1d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2adf5d1d

Branch: refs/heads/trunk
Commit: 2adf5d1df6963b1f9b8dd59f4ce911c1c9456859
Parents: f24e23c 9afd3a5
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:44:34 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:44:52 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--



-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[03/10] cassandra git commit: Use new docker image for CircleCI builds

2018-10-15 Thread spod 
Use new docker image for CircleCI builds

patch by Stefan Podkowinski; reviewed by Marcus Eriksson for CASSANDRA-14713


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dcd92a93
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dcd92a93
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dcd92a93

Branch: refs/heads/cassandra-3.11
Commit: dcd92a93ab12c08963bae8a83340bf7fdfe186dd
Parents: 62e48c5
Author: Stefan Podkowinski 
Authored: Tue Oct 9 14:12:54 2018 +0200
Committer: Stefan Podkowinski 
Committed: Tue Oct 9 14:12:54 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dcd92a93/.circleci/config.yml
--
diff --git a/.circleci/config.yml b/.circleci/config.yml
index f881b70..c389cbc 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -1,10 +1,10 @@
 default_env_vars: _env_vars
-JAVA_HOME: /usr/local/openjdk8u154-cassandra-b02
-ANT_HOME: /usr/local/apache-ant-1.10.1
+JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ANT_HOME: /usr/share/ant
 LANG: en_US.UTF-8
-JDK_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA8_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA7_HOME: /usr/local/openjdk7u82-cassandra-b02
+JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA11_HOME: /usr/lib/jvm/java-11-openjdk-amd64
 KEEP_TEST_DIR: true
 DEFAULT_DIR: /home/cassandra/cassandra-dtest
 PYTHONIOENCODING: utf-8
@@ -68,7 +68,7 @@ workflows:
 build_and_run_tests: *default_jobs
 #build_and_run_tests: *with_dtest_jobs_only
 #build_and_run_tests: *with_dtest_jobs
-docker_image: _image kjellman/cassandra-test:0.4.3
+docker_image: _image spod/cassandra-testing-ubuntu18-java11
 version: 2
 jobs:
   build:
@@ -211,7 +211,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run
@@ -289,7 +289,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[08/10] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

2018-10-15 Thread spod 
Merge branch 'cassandra-3.0' into cassandra-3.11


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/9afd3a5d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/9afd3a5d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/9afd3a5d

Branch: refs/heads/cassandra-3.11
Commit: 9afd3a5d4f2b4e53b284852bbc0157030fe8a625
Parents: 7030356 300fff2
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:42:43 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:43:19 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--



-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[02/10] cassandra git commit: Use new docker image for CircleCI builds

2018-10-15 Thread spod 
Use new docker image for CircleCI builds

patch by Stefan Podkowinski; reviewed by Marcus Eriksson for CASSANDRA-14713


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dcd92a93
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dcd92a93
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dcd92a93

Branch: refs/heads/cassandra-3.0
Commit: dcd92a93ab12c08963bae8a83340bf7fdfe186dd
Parents: 62e48c5
Author: Stefan Podkowinski 
Authored: Tue Oct 9 14:12:54 2018 +0200
Committer: Stefan Podkowinski 
Committed: Tue Oct 9 14:12:54 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dcd92a93/.circleci/config.yml
--
diff --git a/.circleci/config.yml b/.circleci/config.yml
index f881b70..c389cbc 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -1,10 +1,10 @@
 default_env_vars: _env_vars
-JAVA_HOME: /usr/local/openjdk8u154-cassandra-b02
-ANT_HOME: /usr/local/apache-ant-1.10.1
+JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ANT_HOME: /usr/share/ant
 LANG: en_US.UTF-8
-JDK_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA8_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA7_HOME: /usr/local/openjdk7u82-cassandra-b02
+JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA11_HOME: /usr/lib/jvm/java-11-openjdk-amd64
 KEEP_TEST_DIR: true
 DEFAULT_DIR: /home/cassandra/cassandra-dtest
 PYTHONIOENCODING: utf-8
@@ -68,7 +68,7 @@ workflows:
 build_and_run_tests: *default_jobs
 #build_and_run_tests: *with_dtest_jobs_only
 #build_and_run_tests: *with_dtest_jobs
-docker_image: _image kjellman/cassandra-test:0.4.3
+docker_image: _image spod/cassandra-testing-ubuntu18-java11
 version: 2
 jobs:
   build:
@@ -211,7 +211,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run
@@ -289,7 +289,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[06/10] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

2018-10-15 Thread spod 
Merge branch 'cassandra-2.2' into cassandra-3.0


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/300fff27
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/300fff27
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/300fff27

Branch: refs/heads/cassandra-3.0
Commit: 300fff2722ddf2019b428ea0f924aae2eed56016
Parents: ab0e30e dcd92a9
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:41:22 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:41:59 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/300fff27/.circleci/config.yml
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[01/10] cassandra git commit: Use new docker image for CircleCI builds

2018-10-15 Thread spod 
Repository: cassandra
Updated Branches:
  refs/heads/cassandra-2.2 62e48c5f3 -> dcd92a93a
  refs/heads/cassandra-3.0 ab0e30e75 -> 300fff272
  refs/heads/cassandra-3.11 70303563e -> 9afd3a5d4
  refs/heads/trunk f24e23c5f -> 2adf5d1df


Use new docker image for CircleCI builds

patch by Stefan Podkowinski; reviewed by Marcus Eriksson for CASSANDRA-14713


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dcd92a93
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dcd92a93
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dcd92a93

Branch: refs/heads/cassandra-2.2
Commit: dcd92a93ab12c08963bae8a83340bf7fdfe186dd
Parents: 62e48c5
Author: Stefan Podkowinski 
Authored: Tue Oct 9 14:12:54 2018 +0200
Committer: Stefan Podkowinski 
Committed: Tue Oct 9 14:12:54 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dcd92a93/.circleci/config.yml
--
diff --git a/.circleci/config.yml b/.circleci/config.yml
index f881b70..c389cbc 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -1,10 +1,10 @@
 default_env_vars: _env_vars
-JAVA_HOME: /usr/local/openjdk8u154-cassandra-b02
-ANT_HOME: /usr/local/apache-ant-1.10.1
+JAVA_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+ANT_HOME: /usr/share/ant
 LANG: en_US.UTF-8
-JDK_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA8_HOME: /usr/local/openjdk8u154-cassandra-b02
-JAVA7_HOME: /usr/local/openjdk7u82-cassandra-b02
+JDK_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA8_HOME: /usr/lib/jvm/java-8-openjdk-amd64
+JAVA11_HOME: /usr/lib/jvm/java-11-openjdk-amd64
 KEEP_TEST_DIR: true
 DEFAULT_DIR: /home/cassandra/cassandra-dtest
 PYTHONIOENCODING: utf-8
@@ -68,7 +68,7 @@ workflows:
 build_and_run_tests: *default_jobs
 #build_and_run_tests: *with_dtest_jobs_only
 #build_and_run_tests: *with_dtest_jobs
-docker_image: _image kjellman/cassandra-test:0.4.3
+docker_image: _image spod/cassandra-testing-ubuntu18-java11
 version: 2
 jobs:
   build:
@@ -211,7 +211,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run
@@ -289,7 +289,7 @@ jobs:
 export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
 export CASS_DRIVER_NO_EXTENSIONS=true
 export CASS_DRIVER_NO_CYTHON=true
-pip3 install --exists-action w -r 
~/cassandra-dtest/requirements.txt
+pip3 install --upgrade -r ~/cassandra-dtest/requirements.txt
 pip3 freeze
   - run:
   name: Determine Tests to Run


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[07/10] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

2018-10-15 Thread spod 
Merge branch 'cassandra-2.2' into cassandra-3.0


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/300fff27
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/300fff27
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/300fff27

Branch: refs/heads/trunk
Commit: 300fff2722ddf2019b428ea0f924aae2eed56016
Parents: ab0e30e dcd92a9
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:41:22 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:41:59 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/300fff27/.circleci/config.yml
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[09/10] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

2018-10-15 Thread spod 
Merge branch 'cassandra-3.0' into cassandra-3.11


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/9afd3a5d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/9afd3a5d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/9afd3a5d

Branch: refs/heads/trunk
Commit: 9afd3a5d4f2b4e53b284852bbc0157030fe8a625
Parents: 7030356 300fff2
Author: Stefan Podkowinski 
Authored: Mon Oct 15 09:42:43 2018 +0200
Committer: Stefan Podkowinski 
Committed: Mon Oct 15 09:43:19 2018 +0200

--
 .circleci/config.yml | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)
--



-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14790) LongBufferPoolTest burn test fails assertion

2018-10-15 Thread Dinesh Joshi (JIRA) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Joshi updated CASSANDRA-14790:
-
Reviewers: Dinesh Joshi

> LongBufferPoolTest burn test fails assertion
> 
>
> Key: CASSANDRA-14790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14790
> Project: Cassandra
>  Issue Type: Test
>  Components: Testing
> Environment: Run under macOS 10.13.6, with patch (attached, but also 
> https://github.com/jonmeredith/cassandra/tree/failing-burn-test)
>Reporter: Jon Meredith
>Priority: Major
>  Labels: pull-request-available
> Attachments: 0001-Add-burn-testsome-target-to-build.xml.patch, 
> 0002-Initialize-before-running-LongBufferPoolTest.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The LongBufferPoolTest from the burn tests fails with an assertion error.  I 
> added a build target to run individual burn tests, and \{jasobrown} gave a 
> fix for the uninitialized test setup (attached), however the test now fails 
> on an assertion about recycling buffers.
> To reproduce (with patch applied)
> {{ant burn-testsome 
> -Dtest.name=org.apache.cassandra.utils.memory.LongBufferPoolTest 
> -Dtest.methods=testAllocate}}
> Output
> {{    [junit] Testcase: 
> testAllocate(org.apache.cassandra.utils.memory.LongBufferPoolTest): FAILED}}
> {{    [junit] null}}
> {{    [junit] junit.framework.AssertionFailedError}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Debug.check(BufferPool.java:204)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.assertAllRecycled(BufferPool.java:181)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate(LongBufferPoolTest.java:350)}}
> {{    [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate(LongBufferPoolTest.java:54)}}
> All major branches from 3.0 and later have issues, however the trunk branch 
> also warns about references not being released before the reference is 
> garbage collected.
> {{[junit] ERROR [Reference-Reaper:1] 2018-09-25 13:59:54,089 Ref.java:224 - 
> LEAK DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@7f58d19a) to @623704362 was 
> not released before the reference was garbage collected}}
> {{ [junit] ERROR [Reference-Reaper:1] 2018-09-25 13:59:54,089 Ref.java:255 - 
> Allocate trace org.apache.cassandra.utils.concurrent.Ref$State@7f58d19a:}}
> {{ [junit] Thread[pool-2-thread-24,5,main]}}
> {{ [junit] at java.lang.Thread.getStackTrace(Thread.java:1559)}}
> {{ [junit] at 
> org.apache.cassandra.utils.concurrent.Ref$Debug.(Ref.java:245)}}
> {{ [junit] at 
> org.apache.cassandra.utils.concurrent.Ref$State.(Ref.java:175)}}
> {{ [junit] at org.apache.cassandra.utils.concurrent.Ref.(Ref.java:97)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.setAttachment(BufferPool.java:663)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.get(BufferPool.java:803)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$Chunk.get(BufferPool.java:793)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool$LocalPool.get(BufferPool.java:388)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.maybeTakeFromPool(BufferPool.java:143)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.takeFromPool(BufferPool.java:115)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.BufferPool.get(BufferPool.java:85)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$3.allocate(LongBufferPoolTest.java:296)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$3.testOne(LongBufferPoolTest.java:246)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:399)}}
> {{ [junit] at 
> org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:379)}}
> {{ [junit] at java.util.concurrent.FutureTask.run(FutureTask.java:266)}}
> {{ [junit] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}}
> {{ [junit] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}}
> {{ [junit] at java.lang.Thread.run(Thread.java:748)}}
>  
> Perhaps the environment is not being set up correctly for the tests.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org