cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11437) Make number of cores used for copy tasks visible
Date Wed, 13 Apr 2016 01:00:34 GMT

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

Stefania commented on CASSANDRA-11437:
--------------------------------------

[~mambocab], gentle ping to make sure this hasn't gone unnoticed. The dtest patch was reviewed,
the C* patch still needs review, it consists of 2 {{printdebug}} calls that enable detecting
the number of cores in the tests.

> Make number of cores used for copy tasks visible
> ------------------------------------------------
>
>                 Key: CASSANDRA-11437
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11437
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Jim Witschey
>            Assignee: Stefania
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>
> As per this conversation with [~Stefania]:
> https://github.com/riptano/cassandra-dtest/pull/869#issuecomment-200597829
> we don't currently have a way to verify that the test environment variable {{CQLSH_COPY_TEST_NUM_CORES}}
actually affects the behavior of {{COPY}} in the intended way. If this were added, we could
make our tests of the one-core edge case a little stricter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message