template of an issue report

Template of an issue report

Purpose

• What purpose of LeoFS do you use?
  • Test
  • Production
  • Others

Environments

• LeoFS version
  • ref: Available releases of LeoFS
• Erlang version
  • ref: Available releases of Erlang
• What kind of virtualization(VMWare/Docker/Xen...) are you using or using a bare metal?
• What operating system(uname -a) and processor architecture(cat /proc/cpuinfo) and memory(cat /proc/meminfo) are you using?

What happened and How to reproduce if possible

• What did you do?
  • High CPU Load Average
  • High IO Wait
  • Almost Disk Full (90% or more)
  • Output Huge Amount Error Logs (A Large Size File)
  • Suddenly Increase Memory Usage
  • Gradually Increase Memory Usage (Possibility of Memory Leak)
  • Migration Failure
    • Input both the current version and the new version
  • Others - If you've faced other issues, share the situations.
• Screenshot(s) of your monitoring-tool during the issue
  • Input URLs of the screenshots
• What did you expect to see?
• What did you see instead?

System information

• Attach the result of a status command(leofs-adm status).
• Attach the result of a status command to a specific node - leofs-adm status $nodename as necessary.
• Attach command histories.(grep leofs-adm)
• Attach configuration files, leo_(gateway|storage|manager).conf as necessary.
• Attach the result of a specific leofs-adm command - dump-ring, whereis, mq-stats and other as necessary.
• Attach error log files if that exists.
• Attach a erl_crash.dump file if that exists.
• Attach a syslog(dmesg) if something related to Erlang are output.