*** Bug 1440548 has been marked as a duplicate of this bug. ***
@mwringe, This bug is similiar with bug "1439912" with different OCP version, in that bug, @juzhao is asking if the following scenario is ok to cover the test for bug: ### Thanks a lot, I see compaction_large_partition_warning_threshold_mb=100 in hawkular-cassandra pod log, I think we can verify this fix by the following steps: 1. Create a lot of projects to consume memory, CPU and network resources, so data can be kept in cassandra partition. 2. Check the hawkular-cassandra and hawkular-metrics pod logs, make sure there are no such warn info "WARN 18:29:53 Writing large partition hawkular_metrics/metrics_idx:ops-health-monitoring:2 (****** bytes)" Do you think my solution is well enough to verify this defect? ### So my question is also does above steps ok to verify the bug? Thanks, lizhou
@jsanda: can you provide a test case which can be used to verify this is fixed?
Vlaad(vlaad) created 6500 pods and deleted them under one project, and I checked the hawkular-cassandra and hawkular-metrics pod logs, there were no such warn info exists: "WARN 18:29:53 Writing large partition hawkular_metrics/metrics_idx:ops-health-monitoring:2 (****** bytes)" Set it to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1235
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days