G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In Proceedings of the 7th International WWW Conference, April 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the user. This system provides scalability and transparency, but requires some internal mechanism that dynamically assigns client requests to the Web server that can offer the best service [5, 8] The assignment decision can be taken at the IP level through some address packet rewriting mechanism [8, 11], or at the Domain Name System (DNS) level through the mapping of the URL name to the IP address of one of the servers in the cluster [1, 4, 5] Both choices have some drawbacks. The IP dispatcher based systems have full control on the incoming requests, but they can be applied only to locally ....

....in the cluster [1, 4, 5] Both choices have some drawbacks. The IP dispatcher based systems have full control on the incoming requests, but they can be applied only to locally clustered Web servers. The exception is the Network Dispatcher approach which can support multiple Network Dispatchers [11]. Moreover, the task of rewriting all packets can cause the IP dispatcher to become a bottleneck when the system is subject to heavy request load. The DNSdispatcher based clusters do not present risks of bottleneck, and can easily scale from locally to geographically distributed Web server ....

G.D.H. Hunt, G.S. Goldszmidt, R.P. King, R. Mukherjee, "Network Dispatcher: A connection router for scalable Internet services", Proc. of WWW7, Brisbane, Apr. 1998.

....to use the feedback to drive future decisions of where to place load. These have to be designed to prevent load oscillations and to provide stable behavior under a variety of conditions. Although the problem of web server selection has been researched in the past [1] 2] 3] 4] 5] 6] [7] in the context of an Internet wide distributed system, there are several aspects of service composition that make our work novel. First, we have to choose a set of service instances to form a service level path, and not just a single webmirror. Second, composed client sessions could involve ....

....for the choice among wide area distributed replicas have been studied. Several mechanisms have been proposed for load balancing of distributed web server systems [1] These include clientbased approaches [2] 3] 4] DNS based approaches [5] 6] as well as dispatcher based approaches [7]. Service composition involves at least two novel aspects that pose new challenges. First, unlike web mirror selection, we have to choose a set of service instances for each client. Second, we consider failure detection and recovery of composed service in the middle of a long lived session. These ....

G. D. H. Hunt et al., "Network Dispatcher: A Connection Router for Scalable Internet Services," Computer Networks and ISDN Systems, 1998.

....This chapter investigates the techniques of providing efficient load balancing support for accessing replicated services inside the service cluster. A large amount of work has been done by the industry and research community to optimize HTTP request distribution among a cluster of Web servers [11, 12, 21, 38, 53, 64]. Most load balancing policies proposed in such a context rely on the premise that all network packets go through a single frontend dispatcher or a TCP aware (layer 4 or above) switch so that TCP level connection based statistics can be accurately maintained. In contrast, clients and servers ....

....trace. The improvement is 5.2 if the polling time is excluded. Note that the performance results shown in Figure 3.5 are not with discarding slow responding polls. HTTP load balancing. A large body of work has been done to optimize HTTP request distribution among a cluster of Web servers [11, 12, 21, 38, 53, 64]. Most load balancing policies proposed in such a context rely on 52 the premise that all network packets go through a single front end dispatcher or a TCP aware (layer 4 or above) switch so that TCP level connection based statistics can be accurately maintained. However, clients and servers ....

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network Dispatcher: A Connection Router for Scalable Internet Services. In Proc. of the 7th Intl. World Wide Web Conf., Brisbane, Australia, April 1998.

.... applications The model assumptions above are consistent with those of validated stochastic models used to study a wide range of high volume Web sites [13, 25] These papers analyze the performance of special event Web sites (1998 Winter Olympics) governed by IBM s Network Dispatcher product [12], a high speed router which immediately routes each incoming Web requests to one of several host servers. Immediate dispatching of jobs is important in this setting for scalability and efficiency; the router must not become a bottleneck. Our model is also motivated by servers for high performance ....

G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In Proceedings of the 7th International WWW Conference, April 1998.

.... Alteon WebSystems GSLB [3] Resonate s Global Dispatcher [33] F5 Networks 3DNS [19] HydraWeb Techs [23] Radware WSD [31] IBM Network Dispatcher [26] Foundry Networks [21] For the case of multiple Web servers at the same location (Web clusters) various Web switch solutions are described in [12, 17, 22, 35, 29]. The Web switch has a full control on the incoming requests. However, this approach is best suitable to a locally distributed Web server system. Moreover, the Web switch can become the system bottleneck if the Web site is subject to high request rates and there is one dispatching mechanism. In ....

G.D.H. Hunt, G.S. Goldszmidt, R.P. King, R. Mukherjee, \Network Dispatcher: A connection router for scalable Internet services", Proc. of 7th Int. World Wide Web Conf. (WWW7), Melbourne, Australia, Apr. 1998.

....accelerators consist of a load balancer and a cache. The load balancer presents a single IP address to clients regardless of the number of back end servers and routes Web requests to the accelerator cache and back end Web servers. The load bal ancer takes on two basic forms: i) A TCP router [6,11], which for performance reasons does not examine the contents of a Web request, and (ii) a content router [24] which routes requests based on the URL requested. If the requested page is found in the cache, the page is returned to the client. Otherwise, the load balancer routes the request to a ....

....our approach in which all objects are cached in main memory and multiple processors are used to scale the size of main memory. There have been a few papers describing enabling technologies which are utilized by our accelerator. The TCP router used to route requests to caches is analyzed in Refs. [6,11]. Content based routing is discussed by Pai et al. in Ref. 24] A key difference in our work is that we analyze the overhead for doing content based routing and present alternative methods for routing requests when the overhead for performing content based routing is likely to make the router ....

G. Hunt, G. Goldszmidt, R. King, R. Mukherjee, Network dispatcher: a connection router for scalable Internet services, Proceedings of the Seventh International World Wide Web Conference, April 1998.

....of server farm architecture. In a server farm, each arriving job (request) is immediately dispatched by a high speed front end router (a.k.a. dispatcher) to exactly one of the servers, which handles the job. Common dispatchers include Cisco s Local Director [5] and IBM s Network Dispatcher [15]. The immediate dispatching of jobs is crucial for scalability and e#ciency; it s important that the router not become a bottleneck. There is typically no communication between servers, which may not even know of each others existence. The rule used by the dispatcher for assigning jobs to ....

G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In Proceedings of the 7th International WWW Conference, April 1998.

....connection routers. The DNS server provides coarse grained load balancing, while the connection routers provide finer grained load balancing. Connection routers also simplify the management of a Web site because back end servers can be added and removed transparently. IBM s Network Dispatcher [32] is one example of a connection router which hides the IP address of back end servers. Network Dispatcher uses Weighted Round Robin for load balancing requests. Using this algorithm, servers are assigned weights. All servers with the same weight receive a new connection before any server with a ....

G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network Dispatcher: A Connection Router for Scalable Internet Services. In Proceedings of the 7th International World Wide Web Conference, April 1998.

....to use the feedback to drive future decisions of where to place load. These have to be designed to prevent load oscillations and to provide stable behavior under a variety of conditions. Although the problem of web server selection has been researched in the past [1] 2] 3] 4] 5] 6] [7] in the context of an Internet wide distributed system, there are several aspects of service composition that make our work novel. First, we have to choose a set of service instances to form a servicelevel path, and not just a single web mirror. Second, composed client sessions could involve ....

....for the choice among wide area distributed replicas have been studied. Several mechanisms have been proposed for load balancing of distributed web server systems [1] These include client based approaches [2] 3] 4] DNS based approaches [5] 6] as well as dispatcherbased approaches [7]. Service composition involves at least two novel aspects that pose new challenges. First, unlike webmirror selection, we have to choose a set of service instances for each client. Second, we consider failure detection and recovery of composed service in the middle of a long lived session. These ....

G.D.H.Huntet al., "Network Dispatcher: A Connection Router for Scalable Internet Services," Computer Networks and ISDN Systems, 1998.

....cluster. The request distribution between wide area external clients and geographically distributed service clusters is out of the scope of this paper. A large amount of work has been done by the industry and research community to optimize HTTP request distribution among a cluster of Web servers [1, 2, 4, 7, 9, 21, 25]. Most load balancing policies proposed in such a context rely on the premise that all network packets go through a single front end dispatcher or a TCP aware (layer 4 or above) switch so that TCP level connection based statistics can be accurately maintained. In contrast, clients and servers ....

....The study of load balancing policies in this paper complements these service infrastructure work by providing efficient load balancing support suitable for all service granularities. A large body of work has been done to optimize HTTP request distribution among a cluster of Web servers [1, 2, 4, 7, 9, 21, 25]. In particular, locality aware request distribution (LARD) has been proposed to strike the balance between data locality and dynamic load balancing for contentbased request distribution [25] Most load balancing policies proposed in such a context rely on the premise that all network packets go ....

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network Dispatcher: A Connection Router for Scalable Internet Services. In Proc. of the 7th Intl. World Wide Web Conf., Brisbane, Australia, Apr. 1998.

....10203944. some load balancing policies. There exist many methods to implement such a request distribution, which can be divided into two categories based on the OSI layer at which the distribution decision is made [10, 11] In layer 4 dispatching, e.g. Magicrouter [2] and Network Dispatcher [21], the decision is made according to the IP address and TCP port number of the client. The dispatcher routes packets to the chosen node, which establishes TCP connection directly with the client. Since the endpoints in a TCP connection cannot be changed, the dispatcher has to route the packets of ....

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network Dispatcher: A connection router for scalable Internet services. In Proceedings of the 7th International World Wide Web Conference, Apr. 1998.

....of the queue, identifies the customer C for which the request is meant, and finds the instance p assigned to C that has the least load factor. If the allocated capacity of p is fully consumed, the request is throttled, else it is forwarded to p. Similar load balancing techniques are described in [CCY99b, HGKM98]. LD receives load and fault information about an instance from the aggregator and new resource allocations from the RM agents. Any reduction in allocation for a customer is taken into account immediately. An increase in allocated capacity, however, is taken into account only after the ....

G. Hunt, G. Goldszmidt, R. King and R. Mukherjee. Network Dispatcher: A Connection Router for Scalable Internet Services. In Proceedings of the 7th International World Wide Web Conference, 1998.

No context found.

G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In Proceedings of the 7th International WWW Conference, April 1998.

No context found.

R. P. King G. D. H. Hunt, G. S. Goldszmidt and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In In Proceedings of the 7th International World Wide Web Conference, April, 1998.

No context found.

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network dispatcher: a connection router for scalable internet services. Comput. Netw. ISDN Syst., 30(1-7):347-- 357, 1998.

No context found.

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network Dispatcher: A connection router for scalable Internet services. In Proceedings of the 7th International World Wide Web Conference, Apr. 1998.

No context found.

G. D. H. Hunt, G. S. Goldszmidt, R. P. King, and R. Mukherjee. Network Dispatcher: A Connection Router for Scalable Internet Services. In Proc. of the 7th Intl. World Wide Web Conf., Brisbane, Australia, Apr. 1998.

No context found.

G.D.H. Hunt, G.S. Goldszmidt, R.P. King, and R. Mukherjee, "Network Dispatcher: A Connection Router for Scalable Internet Services," Proc. Seventh Int'l World Wide Web Conf., Apr. 1998.

No context found.

G.D.H. Hunt, G.S. Goldzsmit, R. K., and Mukherjee, R. Network Dispatcher: A connection router for scalable internet services. Proceedings of 7th Int'l World Wide Web Conference (April 1998).

No context found.

Hunt, G., G. Goldszmidt, R. King, and R. Mukherjee: 1998, `Network Dispatcher: A Connection Router for Scalable Internet Services'. In: Proceedings of the 7th International World Wide Web Conference.

No context found.

Guerney D.H. Hunt, G. S. Goldszmidt, Richard P. King, and Rajat Mukherjee. Network dispatcher: a connection router for scalable internet services. Computer Networks and ISDN Systems, 30(1-7):347-357, April 1998.

No context found.

G. Hunt, G. Goldszmidt, R. King, R. Mukherjee, Network Dispatcher: A Connection Router for Scalable Internet Services, International World Wide Web Conference, 1998.

No context found.

G.D.H. Hunt, G.S. Goldszmidt, R.P. King, R. Mukherjee, \Network Dispatcher: A connection router for scalable Internet services", Proc. of 7th Int'l. World Wide Web Conf. (WWW7), Brisbane, Australia, Apr. 1998.

No context found.

G. Hunt, G. Goldszmidt, R. King, and R. Mukherjee. Network dispatcher: A connection router for scalable internet services. In Proceedings of the 7th International WWW Conference, April 1998.

No context found.

G.D.H. Hunt, G.S. Goldszmidt, R.P. King, and R. Mukherjee. \Network Dispatcher: a connection router for scalable Internet services," Computer Networks and ISDN Systems, 30 (1998), pp. 347-357.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC