You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For safety reasons, cloud service providers will limit the maximum disk space each Pod can use, such as 100GB. When the files for Stream Load are very large, for example, when conducting a 1TB tpch test, if we load 38GB of data at one time with 5 concurrent operations, it will cause Nginx to report an error: "no space left on device."
Additionally, increasing the number of copies is also not feasible, as the storage space of the container's root directory is shared among multiple containers.
Expected behavior
FE Proxy support mount volumes on /tmp directory.
Please complete the following information
Operator Version: v1.9.6
The text was updated successfully, but these errors were encountered:
Describe the bug
For safety reasons, cloud service providers will limit the maximum disk space each Pod can use, such as 100GB. When the files for Stream Load are very large, for example, when conducting a 1TB tpch test, if we load 38GB of data at one time with 5 concurrent operations, it will cause Nginx to report an error: "no space left on device."
Additionally, increasing the number of copies is also not feasible, as the storage space of the container's root directory is shared among multiple containers.
Expected behavior
FE Proxy support mount volumes on
/tmp
directory.Please complete the following information
The text was updated successfully, but these errors were encountered: