av9ash/GitBugs huggingface dataset:
Bug: Update Jolokia agent for Python DTests
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Jul/22 23:05
Resolved: 18/Jul/22 14:46

We started seeing Python DTest failures that point to Jolokia agent. 

In  [one|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/237/workflows/b9eb4a84-b30c-4fd5-9ca9-ea47f114eef0/jobs/1654/tests] of the latest J11 runs I noticed: 
{code:java}
stdout = b"WARNING: An illegal reflective access operation has occurred\nWARNING: Illegal reflective access by org.jolokia.jvma...rt '8778' is already occupied.\nPlease check the standard output of the target process for a detailed error message.\n" stderr = None, retcode = 1{code}
I checked Jolokia  [official page|https://jolokia.org/] and it seems they added the Java 11 support with 1.7 and we are on 1.6 yet.

So I suspect this might be our solution. To be investigated.
Bug: RPM Installation on centos 7 is broken by CASSANDRA-17669
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Jul/22 16:13
Resolved: 28/Oct/22 13:14

With CASSANDRA-17669 adding use of "or" in the dependencies for the RPM so it can depend on java 8 or java 11 it broke installation on CentOS Linux 7.  This is bad because CentOS Linux 7 is the "current" release of CentOS Linux, version 8 was EOL'ed in favor of the new pre-release distribution model being used for CentOS Stream 8.

I don't know what the best answer is here, maybe making a CentOS 7 specific package that reverts back to just java 8 in the requirements?  But I think should needs to be done.
Bug: Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Sep/22 15:17
Resolved: 04/Nov/22 15:18

It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 Python upgrade tests. Those are properly skipped in Jenkins.

Example runs:

[CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] - 3.0 run

[Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] - while typing this I actually noticed [one test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we test 3.0... 

This is good to be fixed for two reasons - reduce the noise so we do not miss legit failures and we should not spend resources to try to run those tests.
Bug: WEBSITE - Update Stargate copy in the Tools section of Ecosystem page
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 22/Sep/22 06:08
Resolved: 26/Oct/22 00:53

This ticket is to capture the work associated with updates to the copy of Apache Cassandra Website's Ecosystem tool, Stargate.

If the copy cannot be updated by October 12, 2022, please contact me or suggest changes in the pull request.
Bug: WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Aug/22 19:28
Resolved: 25/Oct/22 02:26

This ticket is to capture the work associated with fixing broken links on the blog [Apache Cassandra 4.1: Configuration Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:

{quote}
For a full list of affected parameters, mapping of old to new names and supported units and how things work in general, please refer to the [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can still be set with the old name. Wherever the value format was also changed from numeric value to number + unit value, you can still use the old name + the old numeric value format. For a full list of parameter changes/mapping of old to new parameters and what to expect, please refer to the [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}

The correct page to link is https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
Bug: WEBSITE - Fix incorrect tables threshold mentioned in Guardrails blogpost
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 30/Sep/22 10:06
Resolved: 22/Oct/22 22:27

In the [Guardrails Framework|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html] blog post, the sentence:

{quote}
Continuing with the previous example, if we have a hard limit of ten tables ({{tables_warn_threshold: 10}}) and we try ...
{quote}

should spell {{tables_fail_threshold}}  instead of {{tables_warn_threshold}} .
Bug: CircleCI: Allow to specify multiple tests in the test multiplexer
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 30/Sep/22 10:40
Resolved: 18/Oct/22 16:09

As recently [discussed on the mail list|https://lists.apache.org/thread/o166v7nr9lxnzdy5511tv40rr9t6zbrw], it would be useful if we were able to run multiple test classes on the test multiplexer with a single push:
{quote}The multiplexer only allows to run a single test class per push. This is ok
for fixing existing flakies (its original purpose), and for most minor
changes, but it can be quite inconvenient for testing large patches that
add or modify many tests. For example, the patch for CEP-19 directly
modifies 31 test classes, which means 31 CircleCI config pushes. This
number can be somewhat reduced with some wildcards on the class names, but
the process is still quite inconvenient. I guess that other large patches
will find the same problem.
{quote}
The purpose of this ticket is replacing the {{REPEATED_UTEST_CLASS}} environment var by a new {{REPEATED_UTEST_CLASSES}} var that accepts a list of classes, or an equivalent solution.

The same should be done for the analogous {{REPEATED_JVM_UPGRADE_DTEST_CLASS}} and possibly {{{}REPEATED_DTEST_NAME{}}}.
Bug: CircleCI: Increase the default number of repeated test iterations
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 30/Sep/22 10:32
Resolved: 18/Oct/22 16:08

The current default number of iterations in the test multiplexer is 100. That number was arbitrary chosen during CASSANDRA-16625. However, our recent experience has shown that 100 iterations are not enough in many cases, as [discussed in the mail list|https://lists.apache.org/thread/o166v7nr9lxnzdy5511tv40rr9t6zbrw]. The purpose of this ticket is increasing that default number of iterations to something that we consider more useful, possibly 500.
Bug: Test Failure: dtest-large.topology_test.TestTopology.test_stop_decommission_too_few_replicas_multi_dc 
Status: Open
Priority: Normal
Created: 14/Sep/22 15:58

Link to failure: https://ci-cassandra.apache.org/job/Cassandra-4.1/162/testReport/dtest-large.topology_test/TestTopology/test_stop_decommission_too_few_replicas_multi_dc/

Error Message
test teardown failure

Stacktrace
{code}
Unexpected error found in node logs (see stdout for full details). Errors: [[node1] 'ERROR [OptionalTasks:1] 2022-09-13 02:10:09,576 JVMStabilityInspector.java:68 - Exception in thread Thread[OptionalTasks:1,5,OptionalTasks]\njava.lang.AssertionError: Unknown keyspace ks\n\tat org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:339)\n\tat org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:163)\n\tat org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)\n\tat org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:228)\n\tat org.apache.cassandra.db.Keyspace.open(Keyspace.java:163)\n\tat org.apache.cassandra.db.Keyspace.open(Keyspace.java:152)\n\tat com.google.common.collect.Iterators$6.transform(Iterators.java:785)\n\tat com.google.common.collect.TransformedIterator.next(TransformedIterator.java:47)\n\tat org.apache.cassandra.db.SizeEstimatesRecorder.run(SizeEstimatesRecorder.java:74)\n\tat org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:124)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.lang.Thread.run(Thread.java:748)']
{code}
Bug: `DatabaseDescriptor#clientInitialization` should set the `newFailureDetector` (maybe to a NoOpFailureDetector?)
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 28/Jul/22 14:27
Resolved: 10/Aug/22 19:16

With the introduction of a configurable FailureDetector, client users of the {{cassandra-all}} jar now need to call not just `clientInitialization` but also `setDefaultFailureDetector` in order to avoid an NPE when the failure detector is constructed. This is a breaking change from previous versions where this was not necessary.

Calls to {{DatabaseDescriptor#clientInitialization}} should set {{newFailureDetector}} to +something+, either by calling {{setDefaultFailureDetector}} or creating a different (NoOp?) FailureDetector.
Bug: ttl_test.py::TestRecoverNegativeExpirationDate::test_recover_negative_expiration_date_sstables_with_scrub failing on CircleCI
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Jul/22 18:54
Resolved: 13/Jul/22 16:05

It doesn’t appear on Butler, but on 4.0, 4.1, and trunk, {{ttl_test.py::TestRecoverNegativeExpirationDate.test_recover_negative_expiration_date_sstables_with_scrub}} is failing in {{copy_tree}} w/ a {{DistutilsFileError}}.

{noformat}
        if not dry_run and not os.path.isdir(src):
            raise DistutilsFileError(
>                 "cannot copy tree '%s': not a directory" % src)
E           distutils.errors.DistutilsFileError: cannot copy tree 'sstables/ttl_test/3.11': not a directory

/usr/lib/python3.6/distutils/dir_util.py:127: DistutilsFileError
{noformat}

See https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-17706-4.0-CircleCI&filter=all

(This is just vanilla cassandra-4.0 w/ HIGHRES CircleCI settings.)
Bug: Test splits generated with --only-resource-intensive-tests only work on hosts with >= 27GB memory
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 19/Sep/22 21:18
Resolved: 20/Sep/22 11:25

As the title says, [here|https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-dtest-pytest.sh#L87] we use the "only resource intensive" flag to filter to just those tests, but machines with less than 27G will fail [this one|https://github.com/apache/cassandra-dtest/blob/trunk/conftest.py#L113].
Bug: WEBSITE - Add CASSANDRA-15234 config page to Docs nav menu
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Jul/22 00:26
Resolved: 17/Aug/22 22:45

There is no way to navigate to the new configuration page for CASSANDRA-15234 ([Liberating cassandra.yaml Parameters' Names from Their Units|https://cassandra.apache.org/doc/trunk/cassandra/new/configuration.html]) because it is not referenced anywhere.

Unless someone has bookmarked the page, there is no way to find it on the site.

Other doc changes expected:
 * Add a small table with supported units per type as currently we list only the duration's ones and min units for old parameters. We list the supported units only in NEWS.txt.
 * Add info about the RuntimeExceptions we introduced in CASSANDRA-17725 for a few deprecated JMX getters.
 * Add a note for Cassandra developers - "Please ensure that any JMX setters/getters update the Config class properties and not some local copies. Settings Virtual Table reports the configuration loaded at any time from the Config class."
Bug: Add centos 7 docker/build infra
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Jul/22 16:18
Resolved: 12/Aug/22 17:38

For CASSANDRA-17765 we will need CI for centos 7 packages, but also we should support it over (now deprecated) centos 8, because it is supported until 2024 (because centos is weird.)
Bug: ccm logs not being collected to nightlies
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Sep/22 18:02
Resolved: 21/Sep/22 10:39

At least some of the time, Jenkins is failing to collect ccm logs and is uploading a zero byte tar archive to nightlies, for example: https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-dtest/1100/Cassandra-trunk-dtest/label=cassandra-dtest,split=5/

{quote}
09:25:06  + tar -cJf ccm_logs.tar.xz './tmp/*/test/*/logs/*'
09:25:06  tar: ./tmp/*/test/*/logs/*: Cannot stat: No such file or directory
09:25:06  tar: Exiting with failure status due to previous errors
{quote}
Bug: Extra writePreparedStatement call
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Jul/22 16:06
Resolved: 22/Jul/22 16:34

There seems to be a double insert happening in QueryProcessor.storePreparedStatement()

 

[https://github.com/apache/cassandra/blob/ab9ab903fa590409251e97fe075e02a64c8aa4f3/src/java/org/apache/cassandra/cql3/QueryProcessor.java#L788-L791]

 

I think it's intended to only write to prepared statement  table when it's new to the cache vs every prepare call.  Regardless the extra one should be dropped.
Bug: Add a flag for throughput in MiB/s for nodetool setstreamthroughput, getstreamthroughput, setinterdcstreamthroughput and getinterdcstreamthroughput 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 01/Jul/22 14:19
Resolved: 02/Aug/22 01:05

As we agreed not to add new JMX methods for the new config on the mailing list, we need at least new flags for setstreamthroughput and interdcstreamthroughput for the two 4.0 parameters to be set/get also in MiB, not only in megabits.

Thus we will have the option either to use the old version for those 2, or to be able to set/get in MiB all 4 streaming parameters. As of 4.1 supported units for DataRateSpec are MiB/s, B/s, KiB/s, megabit is only for legacy from 4.0 - backward compatibility. 

To be sure we satisfy the requirements around the latest discussions about backward compatibility in tools, I will use this ticket also to make a final pass on the unit changes done, to ensure the probe output is not affected.
----
Final patch consists of:

- Uncomment prepared_statements_cache_size, key_cache_size, counter_cache_size, index_summary_capacity which were
commented out by mistake in a previous patch
- Fix breaking change with cache_load_timeout; cache_load_timeout_seconds <=0 and cache_load_timeout=0 are equivalent
and they both mean disabled
- Deprecate public method setRate(final double throughputMbPerSec) in Compaction Manager in favor of
setRateInBytes(final double throughputBytesPerSec)
- Revert breaking change removal of StressCQLSSTableWriter.Builder.withBufferSizeInMB(int size). Deprecate it in favor
of StressCQLSSTableWriter.Builder.withBufferSizeInMiB(int size)
- Fix precision issues, add new -m flag (for nodetool/setstreamthroughput, nodetool/setinterdcstreamthroughput,
nodetool/getstreamthroughput and nodetoo/getinterdcstreamthroughput), add new -d flags (nodetool/getstreamthroughput, nodetool/getinterdcstreamthroughput, nodetool/getcompactionthroughput)
- Fix a bug with precision in nodetool/compactionstats
- Deprecate StorageService methods and add new ones for stream_throughput_outbound, inter_dc_stream_throughput_outbound,
compaction_throughput_outbound in the JMX MBean `org.apache.cassandra.db:type=StorageService`
- Removed getEntireSSTableStreamThroughputMebibytesPerSec in favor of new getEntireSSTableStreamThroughputMebibytesPerSecAsDouble
in the JMX MBean `org.apache.cassandra.db:type=StorageService`
- Removed getEntireSSTableInterDCStreamThroughputMebibytesPerSec in favor of getEntireSSTableInterDCStreamThroughputMebibytesPerSecAsDouble
in the JMX MBean `org.apache.cassandra.db:type=StorageService`

It is the same for 4.1 and trunk
Bug: compaction_thoughput default value is different in cassandra.yaml and the Config class
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 01/Aug/22 21:28
Resolved: 08/Aug/22 17:29

compaction_throughput (respectively being named compaction_throughput_mb_per_sec in 4.0) needs to have default value of 64MiB/s in the Config class in 4.0, 4.1 and current trunk post CASSANDRA-14902, confirmed with the reviewer.
Bug: Fix flaky dtest - dtest-upgrade.upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_4_0_x_To_indev_4_1_x.test_bootstrap_multidc
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 12/Jul/22 15:34
Resolved: 15/Jul/22 13:12

https://ci-cassandra.apache.org/job/Cassandra-4.1/93/testReport/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestUpgrade_indev_4_0_x_To_indev_4_1_x/test_bootstrap_multidc/

Error Message

test teardown failure

Stacktrace

Unexpected error found in node logs (see stdout for full details). Errors: [[node2] "ERROR [ScheduledTasks:1] 2022-07-11 22:53:45,982 ResourceWatcher.java:64 - Timed run of class org.apache.cassandra.locator.PropertyFileSnitch$1 failed.\norg.apache.cassandra.exceptions.ConfigurationException: Snitch definitions at cassandra-topology.properties do not define a location for this node's broadcast address /127.0.0.2:7000, nor does it provides a default\n\tat org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:191)\n\tat org.apache.cassandra.locator.PropertyFileSnitch$1.runMayThrow(PropertyFileSnitch.java:78)\n\tat org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)\n\tat org.apache.cassandra.utils.ResourceWatcher$WatchedResource.run(ResourceWatcher.java:57)\n\tat org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:124)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.lang.Thread.run(Thread.java:748)"]
Bug: min_tracked_partition_size_bytes should not have the unit suffix
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 06/Jul/22 13:56
Resolved: 15/Jul/22 16:52

min_tracked_partition_size_bytes was added in CASSANDRA-16310. It should have not been added with the unit suffix anymore as confirmed on the commit.

It is also confusing now when users can add unit of their choice. 

We have two options:
 * keep it with annotation and add also version without the suffix
 * rename it as we are still alpha and API changes can be done for bug fixing. Not sure whether we need an approval on the ML for this one.

CC [~ycai] , [~marcuse] and [~dcapwell]
Bug: Fix flaky test: org.apache.cassandra.tools.nodetool.TpStatsTest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 22/Jul/22 16:20
Resolved: 27/Jul/22 17:53


{code}
junit.framework.AssertionFailedError: 
Expecting:
{code}

...

{code}

to contain pattern:
  "ECHO_RSP\D.*[1-9].*"
	at org.apache.cassandra.tools.nodetool.TpStatsTest.testTpStats(TpStatsTest.java:137)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
Bug: WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 25/Aug/22 03:58
Resolved: 26/Sep/22 18:44

This ticket is to capture the work associated with publishing the September 2022 blog "Learn How CommitLog Works in Apache Cassandra"

If this blog cannot be published by the *September 15, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file).
Bug: GeoHashing
Status: Resolved
Priority: Normal
Resolution: Not A Problem
Created: 30/Sep/22 11:36
Resolved: 30/Sep/22 13:21

Dears,

I am trying to do a GeoHash when importing data of longitude & latitude using DSBULK.

My idea was to call the javascript of GeoHash using a Cassandra Function
[http://www.movable-type.co.uk/scripts/geohash.html]

 

 

CREATE or replace FUNCTION encode(lat double, lng double, lth int)
    RETURNS NULL ON NULL INPUT
    RETURNS text
    LANGUAGE javascript
    AS $$
           'Geohash.GeoHash.encode(lat,lng,lth);'
$$

 

Cassandra version i am using is 4.0.6

Thanks in advance
Bug: Revisit EncodingStats use in memtables
Status: Triage Needed
Priority: Normal
Created: 16/Sep/22 12:55

The efficiency of {{EncodingStats}} and its memtable collector can be improved, e.g. to avoid repeatedly checking for the epoch value and creating new non-short-lived objects on modification.

Further, as the stats are only used during flush, it does not make sense to collect them during memtable updates but rather as part of the processing pass at the start of flushes.
Bug: Test Failure: dtest-novnode.transient_replication_test.TestTransientReplicationRepairLegacyStreaming.test_optimized_primary_range_repair
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 27/Sep/22 15:19
Resolved: 27/Sep/22 15:30

[Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/dtest-novnode.transient_replication_test/TestTransientReplicationRepairLegacyStreaming/test_optimized_primary_range_repair/]

Failed 2 times in the last 30 runs. Flakiness: 10%, Stability: 93%

Error Message
{code}
subprocess.CalledProcessError: Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp', '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar', 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port', '8778', 'start', '12172')' returned non-zero exit status 1.
{code}

Stacktrace
{code}
             raise CalledProcessError(retcode, process.args,
                                        output=stdout, stderr=stderr)
E               subprocess.CalledProcessError: Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp', '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar', 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port', '8778', 'start', '12172')' returned non-zero exit status 1.
{code}