Abstract: The present embodiments relate to updating a dataflow interactive cluster with zero downtime. A request to update a first dataflow cluster can be received, and a second dataflow cluster can be generated as a replacement cluster to execute received queries. Generating the second dataflow cluster can include identifying a second series of executor nodes that are configured to execute queries from the gateway node via a second driver node. A first update to a configuration of a host configuration node can be performed to register the second dataflow cluster as an active endpoint and identify the first dataflow cluster as an inactive endpoint. When no active queries exist, a second update to the configuration can be provided to remove the first dataflow cluster from the configuration to direct subsequent queries from the gateway node to the second dataflow cluster.

Abstract: Systems, methods, and computer-readable storage media are disclosed for configuring and managing a remote presentation session server farm. In an example embodiment, a central management server (CMS) receives a task to be carried out on a server farm (e.g. make an otherwise unused server operate as a remote presentation session server). The CMS then validates this request against a model of allowed tasks, and the current configuration of the server farm. Once validated, the CMS converts the task into operations to be carried out by one or more servers of the server farm. The CMS then sends these operations to the respective servers, where the operations are received by an agent process executing on the server. Each agent performs the received operations on the server upon which it executes, and sends an indication of whether the operations were completed successfully to the CMS. The CMS may then update its model and current configuration to reflect the current configuration of the server farm.

Abstract: Systems, methods, and computer-readable storage media are disclosed for configuring and managing a remote presentation session server farm. In an example embodiment, a central management server (CMS) receives a task to be carried out on a server farm (e.g. make an otherwise unused server operate as a remote presentation session server). The CMS then validates this request against a model of allowed tasks, and the current configuration of the server farm. Once validated, the CMS converts the task into operations to be carried out by one or more servers of the server farm. The CMS then sends these operations to the respective servers, where the operations are received by an agent process executing on the server. Each agent performs the received operations on the server upon which it executes, and sends an indication of whether the operations were completed successfully to the CMS. The CMS may then update its model and current configuration to reflect the current configuration of the server farm.