[jira] [Updated] (AMBARI-18407) BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for transferring 307KB response
[ https://issues.apache.org/jira/browse/AMBARI-18407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18407: -- Resolution: Fixed Status: Resolved (was: Patch Available) > BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for > transferring 307KB response > - > > Key: AMBARI-18407 > URL: https://issues.apache.org/jira/browse/AMBARI-18407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18047.patch > > > Ambari UI when logging-in requests the persisted cluster status from the > /api/v1/persist/CLUSTER_CURRENT_STATUS call. On a 800 node cluster this takes > 2s or more to GET. > The majority of time is in the transfer of bytes. > A 3.8s call had a wait time (time to first byte) of 815ms, and content > download time of 2.98s. > We need to see if the download time can be improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18407) BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for transferring 307KB response
[ https://issues.apache.org/jira/browse/AMBARI-18407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18407: -- Status: Patch Available (was: Open) > BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for > transferring 307KB response > - > > Key: AMBARI-18407 > URL: https://issues.apache.org/jira/browse/AMBARI-18407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18047.patch > > > Ambari UI when logging-in requests the persisted cluster status from the > /api/v1/persist/CLUSTER_CURRENT_STATUS call. On a 800 node cluster this takes > 2s or more to GET. > The majority of time is in the transfer of bytes. > A 3.8s call had a wait time (time to first byte) of 815ms, and content > download time of 2.98s. > We need to see if the download time can be improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18407) BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for transferring 307KB response
[ https://issues.apache.org/jira/browse/AMBARI-18407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-18407: -- Attachment: AMBARI-18047.patch > BE: /api/v1/persist/CLUSTER_CURRENT_STATUS takes more than 2s for > transferring 307KB response > - > > Key: AMBARI-18407 > URL: https://issues.apache.org/jira/browse/AMBARI-18407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18047.patch > > > Ambari UI when logging-in requests the persisted cluster status from the > /api/v1/persist/CLUSTER_CURRENT_STATUS call. On a 800 node cluster this takes > 2s or more to GET. > The majority of time is in the transfer of bytes. > A 3.8s call had a wait time (time to first byte) of 815ms, and content > download time of 2.98s. > We need to see if the download time can be improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
