Package

nelson

cleanup

Permalink

package cleanup

Source
package.scala
Linear Supertypes
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. cleanup
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. All

Type Members

  1. type CleanupRow = (Datacenter, Namespace, DeploymentCtx, RoutingGraph)

    Permalink
  2. final case class DeploymentCtx(deployment: Deployment, status: DeploymentStatus, exp: Option[Instant]) extends Product with Serializable

    Permalink
  3. sealed trait ExpirationPolicy extends AnyRef

    Permalink

Value Members

  1. object CleanupCron

    Permalink
  2. object ExpirationPolicy

    Permalink
  3. object ExpirationPolicyProcess

    Permalink
  4. object GarbageCollector

    Permalink

    The GarbageCollector is a process that periodically traverses the CleanupGraph and marks deployments as garbage.

    The GarbageCollector is a process that periodically traverses the CleanupGraph and marks deployments as garbage. Any deployment that is marked as garbage becomes a candidate for cleanup.

  5. object Reaper

    Permalink
  6. object RetainActive extends ExpirationPolicy

    Permalink
  7. object RetainLatest extends ExpirationPolicy

    Permalink
  8. object RetainLatestTwoFeature extends ExpirationPolicy

    Permalink
  9. object RetainLatestTwoMajor extends ExpirationPolicy

    Permalink
  10. object RetainUntilDeprecated extends ExpirationPolicy

    Permalink
  11. object Sweeper

    Permalink

    Infrequently running cleanup of "leaked" data or data which is otherwise unaccounted for.

    Infrequently running cleanup of "leaked" data or data which is otherwise unaccounted for. Unlike the cleanup process (which is optimized for precision and efficiency), the Sweeper is optimized for comprehensiveness over time via repeated execution (even if we miss some "garbage" on execution i, we will eventually clean it up on excution i + N). We only need to ensure that we 1.) cleanup data that was missed during the Cleanup operation and 2.) ensure we aren't progressively leaking resources over the long-term.

    Items that are identified as an "UnclaimedResource" (items that have no obvious owner -- which may or may not be garbage) are NOT deleted but will be tracked and counted by the end of the task. The number of Unclaimed Resources will be recorded as a histogram, to allow us to have visibility of accumulation on such items. In the event that we discover that the amount of Unclaimed Resources is increasing over time this is a possible indication that we have a major leakage signaling the need to modify the sweeper to be more aggressive.

  12. object SweeperDefaults

    Permalink

Inherited from AnyRef

Inherited from Any

Ungrouped