Preventing TCP incast throughput collapse at the initiation, continuation, and termination

  • Authors:
  • Adrian S.-W. Tam;Kang Xi;Yang Xu;H. Jonathan Chao

  • Affiliations:
  • Polytechnic Institute of New York University;Polytechnic Institute of New York University;Polytechnic Institute of New York University;Polytechnic Institute of New York University

  • Venue:
  • Proceedings of the 2012 IEEE 20th International Workshop on Quality of Service
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

Incast applications have grown in popularity with the advancement of data center technology. It is found that the TCP incast may suffer from the throughput collapse problem, as a consequence of TCP retransmission timeouts when the bottleneck buffer is overwhelmed and causes the packet losses. This is critical to the Quality of Service of cloud computing applications. While some previous literature has proposed solutions, we still see the problem not completely solved. In this paper, we investigate the three root causes for the poor performance of TCP incast flows and propose three solutions, one for each at the beginning, the middle and the end of a TCP connection. The three solutions are: admission control to TCP flows so that the flow population would not exceed the network's capacity; retransmission based on timestamp to detect loss of retransmitted packets; and reiterated FIN packets to keep the TCP connection active until the the termination of a session is acknowledged. The orchestration of these solutions prevents the throughput collapse. The main idea of these solutions is to ensure all the on-going TCP incast flows can maintain the self-clocking, thus eliminates the need to resort to retransmission timeout for recovery. We evaluate these solutions and find them work well in preventing the retransmission timeout of TCP incast flows, hence also preventing the throughput collapse.