Abstract: Server-side control of client-side quality-of-service tracking is provided. When a service is being provided to a client device, a server provides aggregation rules to a client device as part of the service. The client device executes instructions in the aggregation rules to collect QoS metrics regarding the service on the client device and to manipulate the QoS metrics to generate aggregated QoS data. The client device reports the aggregated QoS data to a server for storage and analysis.

Abstract: Server-side control of client-side quality-of-service tracking is provided. When a service is being provided to a client device, a server provides aggregation rules to a client device as part of the service. The client device executes instructions in the aggregation rules to collect QoS metrics regarding the service on the client device and to manipulate the QoS metrics to generate aggregated QoS data. The client device reports the aggregated QoS data to a server for storage and analysis.

Abstract: Server-side control of client-side quality-of-service tracking is provided. When an event occurs at a client, a measurement client collects event parameters and generates aggregated measurement data in accordance with aggregation rules that are provided to the measurement client from a server-side measurement service. The measurement client periodically reports the aggregated measurement data to the measurement service for storage and analysis.

Abstract: Techniques are provided for moving an item from one item server to another item server in a distributed storage system, using a location service, APIs, and item states. There are three parties that transact with each other: a source item server, a destination item server, and a location service. Each item stored at the source has a move status, e.g., “stationary”, “source attempting transfer”, “destination accepting transfer”, or “destination attempting transfer”. Similarly, each item stored at the destination also has a move status, e.g., “stationary”, “source attempting transfer”, “destination accepting transfer”, or “destination attempting transfer”. The location service desirably has an entry for every item stored by the storage system. An item's entry may comprise the item's current location (e.g., an identifier of an item server) together with a state, such as “stable” or “attempting transfer”.

Abstract: A searchable storage system indexes data, such as a blob (binary large object) as it is stored. The indexes are stored simultaneously with the data by the same storage mechanism. Data cannot be stored without indexing it. Any indexing technique may be used. The indexes are then used to access the data. This ensures that any inconsistencies can handled at the local level, and are not visible to clients of the system. Data can be put in to, or taken out from, the searchable storage system. Additionally, a query on the data in the searchable storage system may be performed.

Abstract: A global state management service manages replication in a distributed system. A distributed system can have several replica groups. The global state management service manages state associated with each replica group. Data replication is implemented without implementing an instance of a state machine on each device in a replica group. A replica group comprises a primary device and at least one secondary device. Each device in a replica group contains a replica of data of interest. The global state management service manages the allocation of primary and secondary devices. In the absence of a failure in either a primary device or a secondary device, read and write operations are performed without consulting the global state management service. When a failure is detected, the global state management service manages failover.

Abstract: Server-side control of client-side quality-of-service tracking is provided. When an event occurs at a client, a measurement client collects event parameters and generates aggregated measurement data in accordance with aggregation rules that are provided to the measurement client from a server-side measurement service. The measurement client periodically reports the aggregated measurement data to the measurement service for storage and analysis.

Abstract: Techniques are provided for moving an item from one item server to another item server in a distributed storage system, using a location service, APIs, and item states. There are three parties that transact with each other: a source item server, a destination item server, and a location service. Each item stored at the source has a move status, e.g., “stationary”, “source attempting transfer”, “destination accepting transfer”, or “destination attempting transfer”. Similarly, each item stored at the destination also has a move status, e.g., “stationary”, “source attempting transfer”, “destination accepting transfer”, or “destination attempting transfer”. The location service desirably has an entry for every item stored by the storage system. An item's entry may comprise the item's current location (e.g., an identifier of an item server) together with a state, such as “stable” or “attempting transfer”.

Abstract: A global state management service manages replication in a distributed system. A distributed system can have several replica groups. The global state management service manages state associated with each replica group. Data replication is implemented without implementing an instance of a state machine on each device in a replica group. A replica group comprises a primary device and at least one secondary device. Each device in a replica group contains a replica of data of interest. The global state management service manages the allocation of primary and secondary devices. In the absence of a failure in either a primary device or a secondary device, read and write operations are performed without consulting the global state management service. When a failure is detected, the global state management service manages failover.

Abstract: A searchable storage system indexes data, such as a blob (binary large object) as it is stored. The indexes are stored simultaneously with the data by the same storage mechanism. Data cannot be stored without indexing it. Any indexing technique may be used. The indexes are then used to access the data. This ensures that any inconsistencies can handled at the local level, and are not visible to clients of the system. Data can be put in to, or taken out from, the searchable storage system. Additionally, a query on the data in the searchable storage system may be performed.

Abstract: A method and system for dynamically configuring a server computer is provided. A global configuration file is utilized to configure a server computer on a per request basis. When a request is received at a server computer embodying aspects of the present invention, the server computer dynamically configures itself utilizing the contents of a global configuration file. The global configuration file contains configuration settings that may or may not be utilized by the server computer in configuring itself. To determine if particular configuration settings should be utilized by the server computer in configuring itself, the server computer parses rules also contained in the global configuration file. If a rule is evaluated as true, configuration settings associated with the rule are used by the server computer when configuring itself. The server computer can then respond to the request utilizing its dynamic configuration.

Abstract: A method and system for dynamically configuring a server computer is provided. A global configuration file is utilized to configure a server computer on a per request basis. When a request is received at a server computer embodying aspects of the present invention, the server computer dynamically configures itself utilizing the contents of a global configuration file. The global configuration file contains configuration settings that may or may not be utilized by the server computer in configuring itself. To determine if particular configuration settings should be utilized by the server computer in configuring itself, the server computer parses rules also contained in the global configuration file. If a rule is evaluated as true, configuration settings associated with the rule are used by the server computer when configuring itself. The server computer can then respond to the request utilizing its dynamic configuration.

Abstract: A method and apparatus are provided for determining the validity of a global configuration file. In order to verify the global configuration file, the configuration file is first “flattened.” To flatten the configuration file, the rules in the first block of the configuration file are identified. A settings file is then created with the rules set as true. The normal configuration process is then performed on the configuration file. The resulting settings file constitute the flattened settings for the block and are associated with the block. A determination is then made as to whether any conflicting settings, inconsistently set related settings, or syntax errors exist within the flattened settings. If any such settings do exist, an error message is generated. This process is then repeated for each block in the configuration file so that flattened settings are created for each block. A testing block may also be utilized to identify problems with the settings file generate by the testing block.

Abstract: A method and apparatus are provided for determining the validity of a global configuration file. In order to verify the global configuration file, the configuration file is first “flattened.” To flatten the configuration file, the rules in the first block of the configuration file are identified. A settings file is then created with the rules set as true. The normal configuration process is then performed on the configuration file. The resulting settings file constitute the flattened settings for the block and are associated with the block. A determination is then made as to whether any conflicting settings, inconsistently set related settings, or syntax errors exist within the flattened settings. If any such settings do exist, an error message is generated. This process is then repeated for each block in the configuration file so that flattened settings are created for each block. A testing block may also be utilized to identify problems with the settings file generate by the testing block.