Yarn

Supported OS Linux Mac OS Windows

Intégrationv4.1.0

Hadoop Yarn

Présentation

Ce check recueille des métriques à partir de votre YARN ResourceManager, notamment (sans s’y limiter) :

  • Des métriques propres à votre cluster, comme le nombre d’applications lancées, les conteneurs exécutés, les nœuds qui ne sont pas sains, etc.
  • Des métriques propres à une application, comme l’avancement de l’application, le temps d’exécution écoulé, les conteneurs exécutés, la mémoire utilisée, etc.
  • Des métriques propres à vos nœuds, comme les vCores disponibles, la date de dernière vérification de l’état de santé, etc.

Métriques obsolètes

Les métriques yarn.apps.<MÉTRIQUE> ne sont plus utilisées et ont été remplacées par les métriques yarn.apps.<MÉTRIQUE>_gauge. En effet, les métriques yarn.apps étaient envoyées en tant que RATE, et non en tant que GAUGE.

Configuration

Installation

Le check YARN est inclus avec le package de l’Agent Datadog : vous n’avez donc rien d’autre à installer sur votre YARN ResourceManager.

Configuration

Host

Pour configurer ce check lorsque l’Agent est exécuté sur un host :

  1. Modifiez le fichier yarn.d/conf.yaml dans le dossier conf.d/ à la racine du répertoire de configuration de votre Agent.

    init_config:
    
    instances:
      ## @param resourcemanager_uri - string - required
      ## The YARN check retrieves metrics from YARNS's ResourceManager. This
      ## check must be run from the Master Node and the ResourceManager URI must
      ## be specified below. The ResourceManager URI is composed of the
      ## ResourceManager's hostname and port.
      ## The ResourceManager hostname can be found in the yarn-site.xml conf file
      ## under the property yarn.resourcemanager.address
      ##
      ## The ResourceManager port can be found in the yarn-site.xml conf file under
      ## the property yarn.resourcemanager.webapp.address
      #
      - resourcemanager_uri: http://localhost:8088
    
        ## @param cluster_name - string - required - default: default_cluster
        ## A friendly name for the cluster.
        #
        cluster_name: default_cluster
    

    Consultez un exemple de configuration du check pour découvrir la liste complète des options du check, ainsi que leur description.

  2. Redémarrez l’Agent pour commencer à envoyer des métriques YARN à Datadog.

Environnement conteneurisé

Consultez la documentation relative aux modèles d’intégration Autodiscovery pour découvrir comment appliquer les paramètres ci-dessous à un environnement conteneurisé.

ParamètreValeur
<NOM_INTÉGRATION>yarn
<CONFIG_INIT>vide ou {}
<CONFIG_INSTANCE>{"resourcemanager_uri": "http://%%host%%:%%port%%", "cluster_name": "<NOM_CLUSTER>"}
Collecte de logs
  1. La collecte de logs est désactivée par défaut dans l’Agent Datadog. Vous devez l’activer dans datadog.yaml :

    logs_enabled: true
    
  2. Supprimez la mise en commentaire du bloc de configuration des logs du fichier yarn.d/conf.yaml et modifiez les paramètres. Modifiez les valeurs des paramètres type, path et service en fonction de votre environnement. Consultez le fichier d’exemple yarn.d/conf.yaml pour découvrir toutes les options de configuration disponibles.

    logs:
      - type: file
        path: <LOG_FILE_PATH>
        source: yarn
        service: <SERVICE_NAME>
        # To handle multi line that starts with yyyy-mm-dd use the following pattern
        # log_processing_rules:
        #   - type: multi_line
        #     pattern: \d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2},\d{3}
        #     name: new_log_start_with_date
    
  3. Redémarrez l’Agent.

Pour activer les logs pour les environnements Docker, consultez la section Collecte de logs avec Docker.

Validation

Lancez la sous-commande status de l’Agent et cherchez yarn dans la section Checks.

Données collectées

Métriques

yarn.metrics.apps_submitted
(gauge)
The number of submitted apps
Shown as task
yarn.metrics.apps_completed
(gauge)
The number of completed apps
Shown as task
yarn.metrics.apps_pending
(gauge)
The number of pending apps
Shown as task
yarn.metrics.apps_running
(gauge)
The number of running apps
Shown as task
yarn.metrics.apps_failed
(gauge)
The number of failed apps
Shown as task
yarn.metrics.apps_killed
(gauge)
The number of killed apps
Shown as task
yarn.metrics.reserved_mb
(gauge)
The size of reserved memory
Shown as mebibyte
yarn.metrics.available_mb
(gauge)
The amount of available memory
Shown as mebibyte
yarn.metrics.allocated_mb
(gauge)
The amount of allocated memory
Shown as mebibyte
yarn.metrics.total_mb
(gauge)
The amount of total memory
Shown as mebibyte
yarn.metrics.reserved_virtual_cores
(gauge)
The number of reserved virtual cores
Shown as core
yarn.metrics.available_virtual_cores
(gauge)
The number of available virtual cores
Shown as core
yarn.metrics.allocated_virtual_cores
(gauge)
The number of allocated virtual cores
Shown as core
yarn.metrics.total_virtual_cores
(gauge)
The total number of virtual cores
Shown as core
yarn.metrics.containers_allocated
(gauge)
The number of containers allocated
yarn.metrics.containers_reserved
(gauge)
The number of containers reserved
yarn.metrics.containers_pending
(gauge)
The number of containers pending
yarn.metrics.total_nodes
(gauge)
The total number of nodes
Shown as node
yarn.metrics.active_nodes
(gauge)
The number of active nodes
Shown as node
yarn.metrics.lost_nodes
(gauge)
The number of lost nodes
Shown as node
yarn.metrics.unhealthy_nodes
(gauge)
The number of unhealthy nodes
Shown as node
yarn.metrics.decommissioned_nodes
(gauge)
The number of decommissioned nodes
Shown as node
yarn.metrics.rebooted_nodes
(gauge)
The number of rebooted nodes
Shown as node
yarn.apps.progress_gauge
(gauge)
The progress of the application as a percent
Shown as percent
yarn.apps.started_time_gauge
(gauge)
The time in which application started (in ms since epoch)
Shown as millisecond
yarn.apps.finished_time_gauge
(gauge)
The time in which the application finished (in ms since epoch)
Shown as millisecond
yarn.apps.elapsed_time_gauge
(gauge)
The elapsed time since the application started (in ms)
Shown as millisecond
yarn.apps.allocated_mb_gauge
(gauge)
The sum of memory in MB allocated to the applications running containers
Shown as mebibyte
yarn.apps.allocated_vcores_gauge
(gauge)
The sum of virtual cores allocated to the applications running containers
Shown as core
yarn.apps.running_containers_gauge
(gauge)
The number of containers currently running for the application
Shown as container
yarn.apps.memory_seconds_gauge
(gauge)
The amount of memory the application has allocated (megabyte-seconds)
Shown as mebibyte
yarn.apps.vcore_seconds_gauge
(gauge)
The amount of CPU resources the application has allocated (virtual core-seconds)
Shown as core
yarn.apps.progress
(rate)
Deprecated use yarn.apps.progress_gauge instead
Shown as percent
yarn.apps.started_time
(rate)
Deprecated use yarn.apps.startedtimegauge instead
Shown as second
yarn.apps.finished_time
(rate)
Deprecated use yarn.apps.finishedtimegauge instead
Shown as second
yarn.apps.elapsed_time
(rate)
Deprecated use yarn.apps.elapsedtimegauge instead
Shown as second
yarn.apps.allocated_mb
(rate)
Deprecated use yarn.apps.allocatedmbgauge instead
Shown as mebibyte
yarn.apps.allocated_vcores
(rate)
Deprecated use yarn.apps.allocatedvcoresgauge instead
Shown as core
yarn.apps.running_containers
(rate)
Deprecated use yarn.apps.runningcontainersgauge instead
yarn.apps.memory_seconds
(rate)
Deprecated use yarn.apps.memorysecondsgauge instead
Shown as second
yarn.apps.vcore_seconds
(rate)
Deprecated use yarn.apps.vcoresecondsgauge instead
Shown as second
yarn.node.last_health_update
(gauge)
The last time the node reported its health (in ms since epoch)
Shown as millisecond
yarn.node.used_memory_mb
(gauge)
The total amount of memory currently used on the node (in MB)
Shown as mebibyte
yarn.node.avail_memory_mb
(gauge)
The total amount of memory currently available on the node (in MB)
Shown as mebibyte
yarn.node.used_virtual_cores
(gauge)
The total number of vCores currently used on the node
Shown as core
yarn.node.available_virtual_cores
(gauge)
The total number of vCores available on the node
Shown as core
yarn.node.num_containers
(gauge)
The total number of containers currently running on the node
yarn.queue.root.max_capacity
(gauge)
The configured maximum queue capacity in percentage for root queue
Shown as percent
yarn.queue.root.used_capacity
(gauge)
The used queue capacity in percentage for root queue
Shown as percent
yarn.queue.root.capacity
(gauge)
The configured queue capacity in percentage for root queue
Shown as percent
yarn.queue.num_pending_applications
(gauge)
The number of pending applications in this queue
Shown as task
yarn.queue.user_am_resource_limit.memory
(gauge)
The maximum memory resources a user can use for Application Masters (in MB)
Shown as mebibyte
yarn.queue.user_am_resource_limit.vcores
(gauge)
The maximum vCpus a user can use for Application Masters
Shown as core
yarn.queue.absolute_capacity
(gauge)
The absolute capacity percentage this queue can use of entire cluster
Shown as percent
yarn.queue.user_limit_factor
(gauge)
The minimum user limit percent set in the configuration
yarn.queue.user_limit
(gauge)
The user limit factor set in the configuration
yarn.queue.num_applications
(gauge)
The number of applications currently in the queue
Shown as task
yarn.queue.used_am_resource.memory
(gauge)
The memory resources used for Application Masters (in MB)
Shown as mebibyte
yarn.queue.used_am_resource.vcores
(gauge)
The vCpus used for Application Masters
Shown as core
yarn.queue.absolute_used_capacity
(gauge)
The absolute used capacity percentage this queue is using of the entire cluster
Shown as percent
yarn.queue.resources_used.memory
(gauge)
The total memory resources this queue is using (in MB)
Shown as mebibyte
yarn.queue.resources_used.vcores
(gauge)
The total vCpus this queue is using
Shown as core
yarn.queue.am_resource_limit.vcores
(gauge)
The maximum vCpus this queue can use for Application Masters
Shown as core
yarn.queue.am_resource_limit.memory
(gauge)
The maximum memory resources this queue can use for Application Masters (in MB)
Shown as mebibyte
yarn.queue.capacity
(gauge)
The configured queue capacity in percentage relative to its parent queue
Shown as percent
yarn.queue.num_active_applications
(gauge)
The number of active applications in this queue
Shown as task
yarn.queue.absolute_max_capacity
(gauge)
The absolute maximum capacity percentage this queue can use of the entire cluster
Shown as percent
yarn.queue.used_capacity
(gauge)
The used queue capacity in percentage
Shown as percent
yarn.queue.num_containers
(gauge)
The number of containers being used
yarn.queue.max_capacity
(gauge)
The configured maximum queue capacity in percentage relative to its parent queue
Shown as percent
yarn.queue.max_applications
(gauge)
The maximum number of applications this queue can have
Shown as task
yarn.queue.max_applications_per_user
(gauge)
The maximum number of applications per user this queue can have
Shown as task
yarn.queue.max_active_applications
(gauge)
The maximum number of active applications this queue can have
Shown as task
yarn.queue.max_active_applications_per_user
(gauge)
The maximum number of active applications per user this queue can have
Shown as task

Événements

Le check Yarn n’inclut aucun événement.

Checks de service

yarn.can_connect
Renvoie CRITICAL si l’Agent n’est pas capable de se connecter à l’URI ResourceManager pour recueillir des métriques. Si ce n’est pas le cas, renvoie OK.
Statuses: ok, critical

Dépannage

Besoin d’aide ? Contactez l’assistance Datadog.

Pour aller plus loin