Alexander Dejanovski all time

ebdfcf2027eefeba75efda3cb61a481b49041e0f | Author: Diogenese Topper <diotopper@gmail.com>
 | 2021-09-14 15:08:54-07:00

    Added September 2021 blog post: "Reaper: Anti-entropy Repairs Made Easy" about running repairs using Reaper
    
     patch by Alexander Dejanovski, Diogenese Topper; reviewed by Erick Ramirez, Mick Semb Wever for CASSANDRA-16964

2022cfe073af0a0ba311c80937e6f5c063412200 | Author: Brandon Williams <brandonwilliams@apache.org>
 | 2021-03-04 11:20:07-06:00

    Remove python3:Depends from Debian packaging
    
    Patch by brandonwilliams, reviewed by Alexander Dejanovski for
    CASSANDRA-16480

f4be27fd079690aab67eaac04bd237b1018140a9 | Author: Alexander Dejanovski <alex@thelastpickle.com>
 | 2021-01-27 17:39:11+01:00

    Move excessive repair debug loggings to trace level
    
    Patch by Alexander Dejanovski; reviewed by marcuse for CASSANDRA-16406

7cf35988f298a8ae4ce7ebab2c69e5e7abc28958 | Author: Andrés de la Peña <a.penya.garcia@gmail.com>
 | 2021-01-21 17:10:20+00:00

    Add a jvm upgrade dtest for mixed versions repairs
    
    patch by Andrés de la Peña; reviewed by Yifan Cai and Alexander Dejanovski for CASSANDRA-16244

67f0c3491a4a1966603ace4fe110b7cfc5b64e9c | Author: Alexander Dejanovski <alex@thelastpickle.com>
 | 2020-11-17 10:18:22-08:00

    SSTableLoader will fail if encryption parameters are used due to CASSANDRA-16144
    
    patch by Alexander Dejanovski; reviewed by David Capwell, Jon Meredith for CASSANDRA-16280

45ad38fb5aec76418589c07d88fd0ca27fb430f4 | Author: Swen Fuhrmann <swen.fuhrmann.dev@gmail.com>
 | 2020-09-09 14:19:54+02:00

    On forced shutdown, terminate all repair sessions.
    
    Patch by Swen Fuhrmann, reviewed by Alexander Dejanovski and
    brandonwilliams for CASSANDRA-15902

3cfc8502b82ba88da6ffc69fdad476f7fa0819ca | Author: Jeremy Hanna <jeromatron@gmail.com>
 | 2020-07-07 13:19:55+10:00

    Updated default num_tokens from 256 to 16 with associated allocate_tokens_for_local_replication_factor set to 3
    
     patch by Jeremy Hanna; reviewed by Alexander Dejanovski, Paulo Motta, Brandon Williams, Michael Semb Wever for CASSANDRA-13701

6fc8920889e8537a1f56f45e6c966b3d18325fbb | Author: Alexander Dejanovski <alex@thelastpickle.com>
 | 2020-06-26 11:08:50+02:00

    Fix upgrade failures when using the EC2Snitch in legacy mode
    
    Legacy naming conventions for AWS regions were allowing datacenter names such as us-west and us-west-2, which in the new standard mode become us-west-1 and us-west-2.
    As us-west-2 can match both the standard and legacy mode, checking the DC name cannot be reliably used to detect mixed modes being used as it would fail in case of an upgrade from pre-4.0 clusters in a region such as us-west-2.
    The rack check should be enough as rack names in the standard mode now includes the region name, which can be easily identified.
    
     patch by Alexander Dejanovski; reviewed by Mick Semb Wever, Joey Lynch for CASSANDRA-15878

dd9a6e0a8a691bdee357eb6559f1b2b92b076925 | Author: Jon Haddad jon@jonhaddad.com <jon@jonhaddad.com>
 | 2020-03-24 13:44:17-07:00

    Use more appropriate logging levels.
    
    The following logging was changed:
    
    * When the Commit log reader finishes logging each segment, from debug to info
    * When starting a new compaction, logging details of the compaction task, from debug -> info
    * When finishing a compaction, logging details of how many sstables, sizes, etc, from debug -> info
    * When performing a validation compaction, adding helpful logging
    * When flushing memtables, log details. debug -> info
    * When flushing largest memtable to free up room, logging more details at INFO
    * Various logging messages for incremental repair moved to INFO from debug
    * When failing incremental repair phase, log a warning instead of debug message
    
    Patch by Jon Haddad; Reviewed by Alexander Dejanovski for CASSANDRA-15661

ac77e5e7742548f7c7c25da3923841f59d4b2713 | Author: Alexander Dejanovski <alex@thelastpickle.com>
 | 2018-03-27 12:05:27+02:00

    Downgrade logger.debug calls to logger.trace in the read path
    
    Patch by Alexander Dejanovski; Reviewed by Paulo Motta for CASSANDRA-14318

9d649d69a56a91fcb06a3582b22606f0fe361f49 | Author: Jon Haddad <jon@jonhaddad.com>
 | 2018-02-08 11:01:38-08:00

    Count deleted rows scanned during reads for tracing and tombstone thresholds.
    
    If a row is read but is not live anymore (which happens with row level tombstones) it is not counted anywhere
    in the metrics nor reported in tracing. Row tombstones themselves are not reported anywhere.
    The consequence is that some delete heavy workloads will show no tombstone read but endure severe
    performance issues. This commit counts deleted rows as standard tombstone cells.
    
    Patch by Alexander Dejanovski; Reviewed by Jon Haddad for CASSANDRA-8527

419552a93f4e164dfce3cb6fea15328abade5d3f | Author: Alexander Dejanovski <alex@thelastpickle.com>
 | 2017-12-18 18:27:44+01:00

    Count deleted rows scanned during reads for tracing and warning tombstone thresholds.
    
    If a row is read but is not live anymore (which happens with row level tombstones) it is not counted anywhere
    in the metrics nor reported in tracing. Row tombstones themselves are not reported anywhere.
    The consequence is that some delete heavy workloads will show no tombstone read but endure severe
    performance issues. This commit counts deleted rows as standard tombstone cells.