Andrii Tkach created AMBARI-13391:
-------------------------------------

             Summary: Long API query should be made part of request body
                 Key: AMBARI-13391
                 URL: https://issues.apache.org/jira/browse/AMBARI-13391
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.1.3
            Reporter: Andrii Tkach
            Assignee: Andrii Tkach
            Priority: Critical
             Fix For: 2.1.3


Following API fails with 413 (in some cases 404) error code due to GET request 
URL being too large when there are too many services being installed:
{code}
/api/v1/clusters/mycluster/configurations?(type=hadoop-env&tag=TOPOLOGY_RESOLVED)|(type=hadoop-policy&tag=TOPOLOGY_RESOLVED)|(type=hcat-env&tag=TOPOLOGY_RESOLVED)|(type=hdfs-log4j&tag=TOPOLOGY_RESOLVED)|(type=hdfs-site&tag=TOPOLOGY_RESOLVED)|(type=hive-env&tag=TOPOLOGY_RESOLVED)|(type=hive-exec-log4j&tag=TOPOLOGY_RESOLVED)|(type=hive-log4j&tag=TOPOLOGY_RESOLVED)|(type=hive-site&tag=TOPOLOGY_RESOLVED)|(type=hiveserver2-site&tag=TOPOLOGY_RESOLVED)|(type=mapred-env&tag=TOPOLOGY_RESOLVED)|(type=mapred-site&tag=TOPOLOGY_RESOLVED)|(type=oozie-env&tag=TOPOLOGY_RESOLVED)|(type=oozie-log4j&tag=TOPOLOGY_RESOLVED)|(type=oozie-site&tag=TOPOLOGY_RESOLVED)|(type=pig-env&tag=INITIAL)|(type=pig-log4j&tag=INITIAL)|(type=pig-properties&tag=INITIAL)|(type=ranger-hdfs-audit&tag=TOPOLOGY_RESOLVED)|(type=ranger-hdfs-plugin-properties&tag=TOPOLOGY_RESOLVED)|(type=ranger-hdfs-policymgr-ssl&tag=TOPOLOGY_RESOLVED)|(type=ranger-hdfs-security&tag=TOPOLOGY_RESOLVED)|(type=ranger-hive-audit&tag=TOPOLOGY_RESOLVED)|(type=ranger-hive-plugin-properties&tag=TOPOLOGY_RESOLVED)|(type=ranger-hive-policymgr-ssl&tag=TOPOLOGY_RESOLVED)|(type=ranger-hive-security&tag=TOPOLOGY_RESOLVED)|(type=ranger-yarn-audit&tag=INITIAL)|(type=ranger-yarn-plugin-properties&tag=INITIAL)|(type=ranger-yarn-policymgr-ssl&tag=INITIAL)|(type=ranger-yarn-security&tag=INITIAL)|(type=spark-defaults&tag=INITIAL)|(type=spark-env&tag=INITIAL)|(type=spark-javaopts-properties&tag=INITIAL)|(type=spark-log4j-properties&tag=INITIAL)|(type=spark-metrics-properties&tag=INITIAL)|(type=sqoop-env&tag=INITIAL)|(type=ssl-client&tag=TOPOLOGY_RESOLVED)|(type=ssl-server&tag=TOPOLOGY_RESOLVED)|(type=tez-env&tag=INITIAL)|(type=tez-site&tag=INITIAL)|(type=webhcat-env&tag=TOPOLOGY_RESOLVED)|(type=webhcat-log4j&tag=TOPOLOGY_RESOLVED)|(type=webhcat-site&tag=TOPOLOGY_RESOLVED)|(type=yarn-env&tag=INITIAL)|(type=yarn-log4j&tag=INITIAL)|(type=yarn-site&tag=INITIAL)|(type=zoo.cfg&tag=INITIAL)|(type=zookeeper-env&tag=INITIAL)|(type=zookeeper-log4j&tag=INITIAL)&_=1444342364222
{code}

This leads to UI failing too load the current applied configs to the cluster on 
Add service wizard 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to