Skip to content

Latest commit

 

History

History
73 lines (50 loc) · 2.5 KB

troubleshooting.md

File metadata and controls

73 lines (50 loc) · 2.5 KB

Troubleshooting

You may encounter various problems during installation or development in Fluid. Usually, logs are useful for debugging. But the Runtime containers where Fluid's underlying Distributed Cache Engine is running, are distributed on different hosts under distributed environment, so it's quite annoying to collect these logs one by one. To make this troublesome work easier, we provided a shell script to help users collect logs more quickly. This document describes how to use that script.

Alluxio:

wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-alluxio.sh

JuiceFS:

wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-juicefs.sh

GooseFS:

wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-goosefs.sh

JindoFS:

wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-jindo.sh

Diagnose Fluid using Script

  1. Fluid provides different diagnostic scripts for different Runtimes, but the usage is the same. You can download the runtime diagnostic scripts you use:

    # Alluxio:
    wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-alluxio.sh
    # JuiceFS:
    wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-juicefs.sh
    # GooseFS:
    wget https://raw.githubusercontent.com/fluid-cloudnative/fluid/master/tools/diagnose-fluid-goosefs.sh
  2. Make sure that script is executable, take diagnose-fluid-alluxio.sh as an example:

    $ chmod a+x diagnose-fluid-alluxio.sh
  3. Get help message

    $ ./diagnose-fluid-alluxio.sh
    Usage:
        ./diagnose-fluid-alluxio.sh COMMAND [OPTIONS]
    COMMAND:
        help
            Display this help message.
        collect
            Collect pods logs of controller and runtime.
    OPTIONS:
        -r, --name name
            Set the name of runtime.
        -n, --namespace name
            Set the namespace of runtime.
  4. Collect logs

    You can collect all the Runtime container logs for given name and namespace with:

    $ ./diagnose-fluid-alluxio.sh collect --name cifar10 --namespace default

    NOTES:

    As you can see from above command and help message, option --name and --namespace specified the name and namespace of Alluxio Runtime respectively.

    All the logs will be packed in a package under execution path.