Jaroslaw Grabowski cassandra_src all time

3cfb2221223a7631f116108aec0a45646e775705 | Author: Jaroslaw Grabowski <jaroslaw.grabowski@datastax.com>
 | 2023-03-09 12:35:48+01:00

    Fix BufferPool.memoryInUse counter
    
    The counter was incorrectly decremented by the size of the unused portion of the provided buffer.
    It is now decremented by the number of bytes actually returned to the pool (that may be different than "size"). The number is calculated as a difference between original and resulting buffer capacity.
    
    patch by Jaroslaw Grabowski <jtgrabowski>, reviewed by Jacek Lewandowski <jacek-lewandowski> for CASSANDRA-18311

957eca2fb53477d56bdc9a97c612f1fbecfb5d41 | Author: Branimir Lambov <branimir.lambov@datastax.com>
 | 2022-11-29 09:41:23+02:00

    Implementation of the Unified Compaction Strategy as described in CEP-26
    
    The approach is documented in the included UnifiedCompactionStrategy.md.
    
    Also included:
    - Generalize prettyPrint to prettyPrintBinary (with 2^10 multiplier,
      e.g. MiB) and prettyPrintDecimal (with 1000 multiplier, e.g. ms)
      that cover the full range of double, and add a parseHumanReadable
      method that can read both.
    
    - CASSANDRA-18123: Fix invalid reuse of metadata collector during flushing
    
    - Fix invalid token range splitting with non-unit weights
    
    - Add flushSizeOnDisk metric
    
    - Add ability to change compaction default in YAML
    
    patch by Alex Sorokoumov, Branimir Lambov, Dimitar Dimitrov and Stefania Alborghetti
    reviewed by Alex Sorokoumov, Jaroslaw Grabowski and Maxwell Guo for CASSANDRA-18397

23512cf3da5e8206d8797841f2238cdd86c13d96 | Author: jtgrabowski <jaroslaw.grabowski@datastax.com>
 | 2021-02-24 18:40:22+00:00

    Prevent parent repair sessions leak
    
    patch by Jaroslaw Grabowski and Berenguer Blasi; reviewed by Ekaterina Dimitrova and Andrés de la Peña for CASSANDRA-16446
    
    Co-authored-by: jtgrabowski <jaroslaw.grabowski@datastax.com>
    Co-authored-by: Bereng <berenguerblasi@gmail.com>

4e5bd572f4cca2831b87d6aa1b322e8ad846d015 | Author: Jaroslaw Grabowski <jaroslaw.grabowski@datastax.com>
 | 2020-05-26 15:15:11+02:00

    Bloom false positive rate includes true negatives
    
    Patch by Jaroslaw Grabowski; reviewed by brandonwilliams and paulo for
    CASSANDRA-15384
    
    Before this change the bloom filter false positive rate was calculated
    without true negatives which resulted in high rates. In an extreme case,
    where all queries return no data, the false positive rate could go up to
    1.0.
    
    This change includes true negatives in [recent] bloom filter false ratio.