Abstract: In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic workload-aware shuffling of message types in message queues in an on-demand services environment in a multi-tenant environment according to one embodiment. In one embodiment and by way of example, a method includes monitoring, in runtime, workload patterns associated with incoming workloads, where each workload is associated with a plurality of message types and the plurality of message types are inspected and processed in a predetermined order. The method may further include collecting, in runtime, information regarding each message type based on a workload pattern of its associated workload, and dynamically shuffling the order based on the information, where shuffling includes ordering a first set of message types having one or more messages ahead of a second set of message types having fewer or no messages.

Abstract: Migration specific action requests to perform a set of migration specific actions are sent from a source system instance to a target system instance. Migration specific action responses are received from the target system instance. Based on the migration specific action responses, traffic lights for resource utilization of the target system instance are determined. Based on the traffic lights, a concurrency limit is determined for the specific time. The concurrency limit is applied to scale a total number of ongoing migration specific actions to be requested of the target system instance at the specific time.

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for facilitating a quorum-based coordination of broker health for management of resources for application servers in an on-demand services environment. In one embodiment and by way of example, a method includes monitoring, via health checkers, health of a cluster of brokers in a distributed environment having application servers in communication over a network, receiving an indication from at least one health checker that a broker is failing, wherein the broker is associated with a cluster of worker nodes, collecting health status reports relating to the broker from the health checkers, examining the health status reports based on a quorum-based voting policy, and classifying the broker as unhealthy if, based on the quorum-based voting policy, a percentage of the health status reports regards the broker as failed, wherein the percentage is greater than a first threshold percentage.

Abstract: Systems and techniques for servicing requests in an environment having multiple application servers each having one or more queues to store indications of requests to be serviced by the application servers. A utilization level is determined for a first application server of the multiple application servers. The utilization level is compared to a pre-selected utilization threshold level. The system determines whether to service requests allocated to other application servers in response to the comparing. At least one request allocated to a second application server for servicing.

Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers.

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.

Abstract: In a computing environment having multiple application servers each having at least one connection agent and at least one pause agent and a database node, detecting an error condition between a first application server from the multiple application servers and the database node. Indicating that the database node is unavailable to stop attempts to access the database node by a first application server. The attempts to access the database node are paused without an indication of the database node being unavailable to a source of the attempt to access the database node. Checking periodically, with the first application server, availability of the database node. Indicating that the database node is available in response to a pre-selected number of successful attempts to contact the database node with the first application server.

Abstract: Systems and techniques for utilizing resource aware queues and/or service sharing in a multi-server environment. According to an example, an application server employs a traffic light metaphor to represent a utilization level of resources of the application server by associating a traffic light with each resource. A mapping is maintained that associates service requests with corresponding sets of affected traffic lights. A deferred queue is maintained for each traffic light to facilitate throttling of service requests directed to the application server that involve a resource that is under pressure. Responsive to receiving a service request directed to the application server, the service request is added directly or indirectly to one of multiple queues maintained in front of the application server based on a priority associated with the service request. Service requests are serviced from the queues in accordance with a priority associated with the queues.

Abstract: Techniques and architectures to provide multiple application servers each having at least one connection agent and at least one enabler agent and at least one database organized as multiple nodes. An error condition between a first connection agent and a first database node is detected. The first connection agent indicates that the first database node is unavailable to stop attempts to access the first database node by a first application server. A first enabler agent periodically checks availability of the first database node. The first database node is indicated as available in response to a pre-selected number of successful attempts to contact the first database node with the first enabler agent. The first database node is accessed with the application server in response to the indication that the first database node is available.

Abstract: Within one or more instances of a computing environment where an instance is a self-contained architecture to provide at least one database with corresponding search and file system. User information from the one or more instances of the computing environment is organized as zones. A zone is based on one or more characteristics of corresponding user information that are different than the instance to which the user information belongs. User information is selectively obfuscated prior to transmitting blocks of data including the obfuscated user information. The selective obfuscation is based on zone information for one or more zones to which the user information belongs.

Abstract: Systems and techniques for utilizing resource aware queues and/or service sharing in a multi-server environment. Requests directed to an application server are received into one or more queues in front of the application server. An acknowledgement of the requests is provided in response to the requests being received by the one or more queues. Metadata associated with the requests is utilized to manage the one or more queues. The requests from the one or more queues are processed based on the metadata.

Abstract: Techniques for partition balancing. Organization identifiers (orgIDs) are acquired for one or more organizations within a multi-organization on-demand services environment having multiple nodes, each of which have one or more partitions. A mapping of the orgIDs to the partitions within the multi-organization on-demand services environment is determined. Resource consumption for the organizations is determined. Resource consumption for the partitions based on the resource consumption of the organization and the mapping of the organization to the partitions is determined. A score for the partitions based on the resource consumption is generated. The partitions are redistributed among the nodes based on the partition scores.

Abstract: Within one or more instances of a computing environment where an instance is a self-contained architecture to provide at least one database with corresponding search and file system. User information from the one or more instances of the computing environment is organized as zones. A zone is based on one or more characteristics of corresponding user information that are different than the instance to which the user information belongs. User information is selectively obfuscated prior to transmitting blocks of data including the obfuscated user information. The selective obfuscation is based on zone information for one or more zones to which the user information belongs.

Abstract: Techniques and architectures to provide multiple application servers each having at least one connection agent and at least one enabler agent and at least one database organized as multiple nodes. An error condition between a first connection agent and a first database node is detected. The first connection agent indicates that the first database node is unavailable to stop attempts to access the first database node by a first application server. A first enabler agent periodically checks availability of the first database node. The first database node is indicated as available in response to a pre-selected number of successful attempts to contact the first database node with the first enabler agent. The first database node is accessed with the application server in response to the indication that the first database node is available.

Abstract: Migration specific action requests to perform a set of migration specific actions are sent from a source system instance to a target system instance. Migration specific action responses are received from the target system instance. Based on the migration specific action responses, traffic lights for resource utilization of the target system instance are determined. Based on the traffic lights, a concurrency limit is determined for the specific time. The concurrency limit is applied to scale a total number of ongoing migration specific actions to be requested of the target system instance at the specific time.

Abstract: Techniques for partition balancing. Organization identifiers (orgIDs) are acquired for one or more organizations within a multi-organization on-demand services environment having multiple nodes, each of which have one or more partitions. A mapping of the orgIDs to the partitions within the multi-organization on-demand services environment is determined. Resource consumption for the organizations is determined. Resource consumption for the partitions based on the resource consumption of the organization and the mapping of the organization to the partitions is determined. A score for the partitions based on the resource consumption is generated. The partitions are redistributed among the nodes based on the partition scores.

Abstract: Techniques and architectures to provide multiple application servers each having at least one connection agent and at least one enabler agent and at least one database organized as multiple nodes. An error condition between a first connection agent and a first database node is detected. The first connection agent indicates that the first database node is unavailable to stop attempts to access the first database node by a first application server. A first enabler agent periodically checks availability of the first database node. The first database node is indicated as available in response to a pre-selected number of successful attempts to contact the first database node with the first enabler agent. The first database node is accessed with the application server in response to the indication that the first database node is available.

Abstract: In a computing environment having multiple application servers each having at least one connection agent and at least one pause agent and a database node, detecting an error condition between a first application server from the multiple application servers and the database node. Indicating that the database node is unavailable to stop attempts to access the database node by a first application server. The attempts to access the database node are paused without an indication of the database node being unavailable to a source of the attempt to access the database node. Checking periodically, with the first application server, availability of the database node. Indicating that the database node is available in response to a pre-selected number of successful attempts to contact the database node with the first application server.

Abstract: Within one or more instances of a computing environment where an instance is a self-contained architecture to provide at least one database with corresponding search and file system. User information from the one or more instances of the computing environment is organized as zones. A zone is based on one or more characteristics of corresponding user information that are different than the instance to which the user information belongs. User information is selectively obfuscated prior to transmitting blocks of data including the obfuscated user information. The selective obfuscation is based on zone information for one or more zones to which the user information belongs.