What Should I Do If a Large File Fails to Be Uploaded on the Hue Page?

Question

A large file fails to be uploaded on the Hue page.

Answer

1. You are not advised to use the Hue browser to upload large files. You are advised to use the client to upload large files using commands.
2. If Hue is required, perform the following steps to modify Httpd parameters:
   1. Log in to the active management node as user omm.
   2. Run the following command to edit the httpd.conf configuration file:

      vi $BIGDATA_HOME/om-server/Apache-httpd-2.4.39/conf/httpd.conf

   3. Search for 21201 and add RequestReadTimeout handshake=0 header=0 body=0 to the </VirtualHost> configuration.

      ...
      <VirtualHost *:21201>
          ServerName https://10.112.16.93:21201
          AllowEncodedSlashes On
          SSLProxyEngine On
          ProxyRequests Off
          TraceEnable off
          ProxyTimeout  1200
          RewriteEngine on
          RewriteMap proxylist dbm:${BIGDATA_ROOT_HOME}/om-server_XXX/Apache-httpd-2.4.39/conf/proxylist.dbm
      
          RewriteRule ^(\/.*)$  ${proxylist:/Hue/Hue/21201}$1 [E=TARGET_PATH:$1,L,P]
      
          Header edit Location ^(?!https://100.112.16.93:20009|https://100.112.16.93:21201)http[s]?://[^/]*(.*)$  https://10.112.16.93:21201$1
      
          ProxyPassReverseCookiePath / / interpolate
      
          SSLEngine On
          SSLProxyProtocol  All +TLSv1.2 -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
          SSLProtocol ALL +TLSv1.2 -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
          SSLCipherSuite ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:DHE-DSS-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256
          SSLProxyCheckPeerName off
          SSLProxyCheckPeerCN off
          SSLCertificateFile "${BIGDATA_ROOT_HOME}/om-server_8.0.2.1/Apache-httpd-2.4.39/conf/security/proxy_ssl.cert"
          SSLCertificateKeyFile "${BIGDATA_ROOT_HOME}/om-server_8.0.2.1/Apache-httpd-2.4.39/conf/security/server.key"
          SSLProxyCACertificateFile ${BIGDATA_ROOT_HOME}/om-server_8.0.2.1/apache-tomcat-8.5.57/conf/security/tomcat.crt
          SSLCertificateChainFile "${BIGDATA_ROOT_HOME}/om-server_8.0.2.1/Apache-httpd-2.4.39/conf/security/proxy_chain.cert"
          RequestReadTimeout handshake=0 header=0 body=0
      </VirtualHost>
      ...

   4. Run the ps -ef|grep httpd|grep -v grep|xargs kill -9 command to restart the httpd.