Identifying and managing transaction conflicts
In a computer-implemented method for configuring a distributed computer system comprising a plurality of nodes of a plurality of node classes, configuration files for a plurality of nodes of each of the plurality of node classes are stored in a central repository. The configuration files include information representing a desired system state of the distributed computer system, and the distributed computer system operates to keep an actual system state of the distributed computer system consistent with the desired system state. The plurality of node classes includes forwarder nodes for receiving data from an input source, indexer nodes for indexing the data, and search head nodes for searching the data. Responsive to receiving changes to the configuration files, the changes are propagated to nodes of the plurality of nodes impacted by the changes based on a node class of the nodes impacted by the changes.
1. A computer-implemented method comprising:
storing configuration files, in a central repository on a management node to enable unification of maintenance of the configuration files, for a plurality of node classes of a distributed computer system that operates to maintain an actual system state of the distributed computer system consistent with a desired system state of the distributed computer system as represented by the configuration files in the central repository;
receiving a transaction comprising a change to a configuration file; and
determining whether the transaction conflicts with the configuration files, wherein when the transaction conflicts with the configuration files, providing a notification that the transaction is not merged into the configuration files, and
when the transaction fails to conflict with the configuration files, merging the transaction into the configuration files for a plurality of nodes of the plurality of node classes impacted by the change to the configuration file to update the desired system state of the distributed computer system.
2. The computer-implemented method of claim 1 , wherein the transaction further comprises acceptance criteria for the change to the configuration file.
3. The computer-implemented method of claim 1 , wherein the configuration files include information representing the desired system state of the distributed computer system.
4. The computer-implemented method of claim 1 , wherein the plurality of node classes include forwarder nodes for receiving data from an input source, indexer nodes for indexing the data, and search head nodes for searching the data.
5. The computer-implemented method of claim 1 , wherein the central repository includes a common configuration file sub-repository for maintaining configuration files common to the plurality of nodes of the plurality of node classes.
6. The computer-implemented method of claim 1 , wherein the transaction is received from a single management node of the distributed computer system.
7. The computer-implemented method of claim 1 , wherein the merging the transaction into the configuration files for a plurality of nodes is performed via a representational state transfer call.
8. The computer-implemented method of claim 1 , wherein when the change to the configuration file impacts search nodes, the transaction is merged into the configuration files for the search nodes.
9. One or more non-transitory computer storage media containing instructions which when executed on one or more data processors, cause the one or more data processors to perform operations comprising:
storing configuration files, in a central repository on a management node to enable unification of maintenance of the configuration files, for a plurality of node classes of a distributed computer system that operates to maintain an actual system state of the distributed computer system consistent with a desired system state of the distributed computer system as represented by the configuration files in the central repository;
receiving a transaction comprising a change to a configuration file; and
determining whether the transaction conflicts with the configuration files, wherein when the transaction conflicts with the configuration files, providing a notification that the transaction is not merged into the configuration files, and
when the transaction fails to conflict with the configuration files, merging the transaction into the configuration files for a plurality of nodes of the plurality of node classes impacted by the change to the configuration file to update the desired system state of the distributed computer system.
10. The one or more non-transitory computer storage media of claim 9 , wherein the transaction further comprises acceptance criteria for the change to the configuration file.
11. The one or more non-transitory computer storage media of claim 9 , wherein the configuration files include information representing the desired system state of the distributed computer system.
12. The one or more non-transitory computer storage media of claim 9 , wherein the plurality of node classes include forwarder nodes for receiving data from an input source, indexer nodes for indexing the data, and search head nodes for searching the data.
13. The one or more non-transitory computer storage media of claim 9 , wherein the central repository includes a common configuration file sub-repository for maintaining configuration files common to the plurality of nodes of the plurality of node classes.
14. The one or more non-transitory computer storage media of claim 9 , wherein the transaction is received from a single management node of the distributed computer system.
15. The one or more non-transitory computer storage media of claim 9 , wherein the merging the transaction into the configuration files for a plurality of nodes is performed via a representational state transfer call.
16. The one or more non-transitory computer storage media of claim 9 , wherein when the change to the configuration file impacts search nodes, the transaction is merged into the configuration files for the search nodes.
17. A system comprising:
one or more data processors; and
one or more non-transitory computer storage media containing instructions which when executed on the one or more data processors, cause the one or more processors to perform operations comprising:
storing configuration files, in a central repository on a management node to enable unification of maintenance of the configuration files, for a plurality of node classes of a distributed computer system that operates to maintain an actual system state of the distributed computer system consistent with a desired system state of the distributed computer system as represented by the configuration files in the central repository;
receiving a transaction comprising a change to a configuration file; and
determining whether the transaction conflicts with the configuration files, wherein when the transaction conflicts with the configuration files, providing a notification that the transaction is not merged into the configuration files, and
when the transaction fails to conflict with the configuration files, merging the transaction into the configuration files for a plurality of nodes of the plurality of node classes impacted by the change to the configuration file to update the desired system state of the distributed computer system.
18. The system of claim 17 , wherein when the change to the configuration file impacts search nodes, the transaction is merged into the configuration files for the search nodes.
19. The system of claim 17 , wherein the central repository includes a common configuration file sub-repository for maintaining configuration files common to the plurality of nodes of the plurality of node classes.
20. The system of claim 17 , wherein the plurality of node classes include forwarder nodes for receiving data from an input source, indexer nodes for indexing the data, and search head nodes for searching the data.