Skip to main content
Version: 3.1.0 (Preview)

Stack and Service Overview

Stack and service descriptors, inheritance, resolved components, packages, dependencies, and lifecycle commands

A Stack version resolves inherited and child service definitions before Ambari assigns components and executes lifecycle commands.

Lifecycle​

Ambari installs and manages a stack version by resolving its services, selecting component hosts, applying configuration dependencies, and invoking component lifecycle commands. A component normally supports install, start, stop, status, and configure operations; custom commands may extend that lifecycle.

Inheritance​

The BIGTOP stack uses stack-level services that may inherit from common-services. A child descriptor can add components or configuration and can override inherited values. Service inheritance is explicit in metainfo.xml; stack inheritance controls the files and directories supplied by a parent stack version.

Telemetry​

The retained metrics.json contract defines a small set of direct-JMX values needed by management workflows. The Prometheus/VictoriaMetrics design uses telemetry.json as the separate time-series collection description. Keep these files distinct: management values are not historical monitoring samples.

Current Provider​

The current metrics provider is VictoriaMetrics, with single-node and distributed components represented by the BIGTOP service definition. Provider packaging and runtime deployment are documented in RPM Packaging. This overview intentionally excludes retired AMS/Ganglia and Ember-specific procedures.