The most likely result of not running cleanup is wasted disk space.
The second most likely result is resurrecting deleted data if you do a second
range movement (expansion, shrink, etc).
If this is bad for you, you should run cleanup now. For many use cases, it’s a
nonissue.
If you know you’
Hi,
I should have run cleanup after adding a few nodes to my cluster, about 2
months ago, the ttl is 6 month, What happens now? Should i worry about any
catastrophics?
Should i run the cleanup now?
Thanks in advance
Sent using https://www.zoho.com/mail/
On 2/12/19 11:53 AM, Michael Shuler wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-14183
>
> 2.1 NEWS.txt merged up:
> https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L21-L28
I should have included that you can try simply replacing the jars in
lib/ with the newer ones. L
https://issues.apache.org/jira/browse/CASSANDRA-14183
2.1 NEWS.txt merged up:
https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L21-L28
--
Kind regards,
Michael
On 2/12/19 2:49 AM, Oleksandr Shulgin wrote:
> Hi,
>
> The latest release notes for all versions mention that logback <
Hello,
I have a materialized view defined by the following:
CREATE MATERIALIZED VIEW m_ps_project_policy_device0 AS
SELECT policy_id, device_id, project_id, namespace,
metric_type, blufi_id, beacon_id, event_uuid, state, date_created,
policy_name, beacon_name, blufi_name, value, duration F
Hi,
The latest release notes for all versions mention that logback < 1.2.0 is
subject to CVE-2017-5929 and that the logback version is not upgraded.
E.g:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.18
Indeed, when installing 3.0.18 from t
