Checkout Tools
  • last updated 2 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OAK-8429 - oak-run check should expose repository statistics for the last good revision
  1. … 1 more file in changeset.
OAK-8358 - oak-run check should have an option for specifying memory mapping
  1. … 2 more files in changeset.
OAK-7719 - Let check use the specified journal consistently
  1. … 5 more files in changeset.
OAK-7866 - Fix comparison of journal entries
OAK-7866 - Check the consistency of the recovered journal
  1. … 1 more file in changeset.
OAK-7918 - Rename ConsistencyCheckerTemplate to ConsistencyChecker
  1. … 2 more files in changeset.
OAK-7918 - Remove ConsistencyChecker

ConsistencyChecker acted as a middleman between the Check command and

ConsistencyCheckerTemplate. It didn't provide any useful functionality outside

of the context of the Check command. This commit merges ConsistencyChcker in

the Check command and removes. Additionally, this commit moves the tests for

the Check command into the o.a.j.o.segment.tool package.

  1. … 10 more files in changeset.
OAK-7918 - Extract ConsistencyCheckerTemplate

The first step in making ConsistencyChecker usable in a programmatic way is to

separate the consistency checking logic from the code that takes care of

argument parsing, progress statements output and result reporting. The

consistency checking logic, unburdened by any other superfluous

responsibilities, has been extracted into a new class,

ConsistencyCheckerTemplate.

  1. … 2 more files in changeset.
OAK-7866 - Introduce the recover-journal command
  1. … 2 more files in changeset.
OAK-7872 - Make LoggingHook private to o.a.j.o.segment
  1. … 5 more files in changeset.
OAK-7864 - Log Segment Store read operations

Contribution by Axel Hanikel.

  1. … 1 more file in changeset.
OAK-7849 - Implement a CommitHook to log commit activity

Contribution by Axel Hanikel

  1. … 2 more files in changeset.
OAK-7834 - Add tool to search for nodes in a Segment Store
  1. … 2 more files in changeset.
OAK-7511: get rid of JSR 305 dependency - use jetbrains nullability annotations instead - oak-segment-tar
  1. … 137 more files in changeset.
fix svn:eol-style
  1. … 2 more files in changeset.
OAK-5655: TarMK: Analyse locality of reference

Add the capability to analyse random IO traces

  1. … 5 more files in changeset.
fix svn:eol-style
  1. … 3 more files in changeset.
OAK-7444: Allow collection of IOTraces during normal operation

* Refactoring of IOTracer and related classes to enable logging IO reads via IOMonitor

* Use logger org.apache.jackrabbit.oak.segment.file.tar.SegmentTarWriter for logging IO reads in debug mode

    • ?
    ./iotrace/DefaultIOTraceWriter.java
  1. … 8 more files in changeset.
fix svn:eol-style
  1. … 1 more file in changeset.
OAK-7402: Expose UI for collecting IO traces

Introduce a iotrace run mode in oak-run

  1. … 5 more files in changeset.
fix svn:eol-style
  1. … 4 more files in changeset.
OAK-5655: TarMK: Analyse locality of reference

Depth first trace

  1. … 3 more files in changeset.
OAK-5655: TarMK: Analyse locality of reference

Typo

  1. … 4 more files in changeset.
OAK-5655: TarMK: Analyse locality of reference

Fixed typo causing bad UUIDs in io traces

OAK-5655: TarMK: Analyse locality of reference

Utility for collecting IO traces for given read access patterns

  1. … 5 more files in changeset.
OAK-7355: Move the pluggable storage interfaces to the SPI package
  1. … 74 more files in changeset.
OAK-7058: oak-run compact reports success even when it was cancelled

Print a message and return 1 on cancellation

OAK-6921: Support pluggable segment storage
  1. … 43 more files in changeset.
OAK-7237 - Let the bakcup and restore commands properly propagate errors

The backup and restore commands should always return with a non-zero return

code in case of error. Moreover, error messages and stack traces should always

be printed on the standard error.

  1. … 2 more files in changeset.
OAK-7236 - Let the diff command properly propagate errors

The diff command should always return with a non-zero return code in case of

error. Moreover, error messages and stack traces should always be printed on

the standard error.

  1. … 1 more file in changeset.