WO2019100596A1

WO2019100596A1 - Method and system for operating distributed system

Info

Publication number: WO2019100596A1
Application number: PCT/CN2018/075499
Authority: WO
Inventors: 刘雄文
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2017-11-23
Filing date: 2018-02-06
Publication date: 2019-05-31
Also published as: CN107947980B; CN107947980A

Abstract

A method for operating a distributed system comprises: a current module operation server receiving a module operation request forwarded by a forwarding server according to a module type; operating, according to the module operation request, a current module to obtain a first module operation result; and returning the first module operation result to the forwarding server, such that the forwarding server transmits the first module operation result to a client terminal of a system.

Description

Distributed system operation method and system

Cross-reference to related applications

The present application claims the priority of the Chinese Patent Application entitled "Distributed System Operation Method and System" by the Chinese Patent Office on November 23, 2017, the entire disclosure of which is incorporated herein by reference. .

Technical field

The application relates to a distributed system operation method and system.

Background technique

A distributed system is a software system built on top of a network. Because of the nature of software, distributed systems are highly cohesive and transparent. In a blockchain or a distributed system based on the PaxOS algorithm protocol, multiple nodes participate in data processing, and a consensus is reached based on the processing strategy and accepted by the system as a whole.

The inventor realized that the traditional distributed system is set up by the R&D personnel in the static environment in advance. After the system is started, if the components in the system need to be changed, the system needs to be shut down first, that is, the static environment is restored, and then Corresponding modifications are made by the R&D personnel, which are inefficient and costly.

Summary of the invention

In accordance with various embodiments disclosed herein, a distributed system operating method and system is provided.

A distributed system operation method includes:

The current component operation server receives the component operation request forwarded by the forwarding server according to the component type;

The current component operation server operates on the current component in the distributed system according to the component operation request to obtain a first component operation result; and

The current component operation server returns the first component operation result to the forwarding server, so that the forwarding server sends the first component operation result to the system client.

A distributed system operating system, including a forwarding server and a current component operation server;

The forwarding server is configured to forward the received component operation request to the current component operation server according to the component type; and

The current component operation server is configured to operate the current component in the distributed system according to the component operation request to obtain a first component operation result; and return the first component operation result to the forwarding server, so as to The forwarding server sends the first component operation result.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is an application scenario diagram of a distributed system operation method in accordance with one or more embodiments.

2 is a flow diagram of a method of operating a distributed system in accordance with one or more embodiments.

FIG. 3 is a schematic diagram of component association in accordance with one or more embodiments.

4 is a flow diagram of a transaction request processing step in accordance with one or more embodiments.

5 is a flow diagram of transaction request processing steps and component operation request processing steps in accordance with one or more embodiments.

Detailed ways

In order to make the technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

Please refer to FIG. 1. FIG. 1 is a schematic diagram of an application scenario of a distributed system operation method according to an embodiment. FIG. 1 shows a system client, a forwarding server, a plurality of component servers corresponding to component types, a request response server, and a request server. .

The system client can receive the component operation request sent by the administrator terminal by means of the message, and can also receive the transaction request by means of the message. When the system client receives the component operation request sent by the administrator terminal, it first needs to determine whether the user who sends the component operation request has the administrator authority. Only after having the administrator authority, the system client sends the component operation request to Forward the server. When the system client receives the transaction request, it forwards the transaction request to the request response server, so that the request response server forwards the transaction request to the request server for processing. In order to ensure the security of the message, the component operation request and the transaction request are processed by encryption and signing, and after the system finishes processing the request, the system client takes the result of the component operation and the result of the request processing. The user sent to the system client separately.

The forwarding server is configured to receive the component operation request, verify the login of the administrator user, check and decrypt the packet, and distribute the component operation request to the corresponding component operation server according to the component type. After the component operation server completes the operation of the corresponding component, the corresponding operation result is forwarded to the system client.

The key components in a distributed system include channels, nodes, organizations, users, and sort servers. Therefore, component operation servers include channel operation servers, node operation servers, organization operation servers, user operation servers, and sort server operation servers. Different component operation servers operate the components according to the component operation requests, and feed back the operation results to the forwarding server. The channel in the distributed system is used to receive the transaction request sent by the requesting server, and send the transaction request to all the nodes in the channel, and the node processes the transaction request to obtain the preliminary transaction result, and returns the preliminary transaction result to the channel. The channel obtains the target transaction result according to the preliminary transaction result and sends it to the sorting server. The sorting server sorts and stores the target transaction result in chronological order, and the node can obtain the corresponding target transaction result from the sorting server, wherein the user can be in the organization. To register, the organization assigns a node to the registered user, that is, establishes a mapping relationship between the user and the node, and the node is assigned to a different channel according to the transaction type.

The request response server receives the transaction request sent by the system client, decrypts and checks the request message, ensures the validity of the message, and requests the server to assign a unique transaction identifier to each transaction request, for example, may be a transaction. ID number, etc., and receive the target transaction result returned by the transaction server, establish a mapping relationship between the transaction identifier and the target transaction result.

The trading server selects the appropriate channel based on the type of the transaction request, and then sends the transaction request to all available trading nodes in the channel through the channel, so that the trading node can process the transaction request to obtain the preliminary transaction result, and the preliminary transaction result Feedback to the channel, the channel calculates the target transaction result based on the obtained preliminary transaction result, and feeds back to the transaction server, which is returned by the transaction server to the transaction response server, and is fed back to the system client by the transaction response server. And the transaction server can also receive the component operation result of the forwarding server or the channel operation server or other component operation server in the process of processing the transaction, and then adjust the processing manner of the current transaction request according to the component operation result.

The servers and the like involved above may exist in the form of a server cluster to prevent a single point of failure from causing a system failure or the like.

In one embodiment, referring to FIG. 2, a distributed system operation method is provided. This embodiment is exemplified by applying the method to the component operation server in FIG. 1 described above. The component operation server runs a distributed system operation readable instruction through which the distributed system operation method is implemented by operating the readable instructions. The method specifically includes the following steps:

S202: The current component operation server receives the component operation request forwarded by the forwarding server according to the component type.

Referring to FIG. 1, when the system client receives the component operation request, the component operation request may be sent to the forwarding server, and after receiving the component operation request, the forwarding server may first verify whether the user who sends the component operation request has Administrator authority, if there is no administrator authority, return the result of the operation failure; if there is administrator authority, the component operation request is checked and decrypted to obtain the plaintext of the component operation request, and the forwarding server is represented according to the plaintext The component type forwards the component operation request to the corresponding current component operations server.

The component types of the distributed system include channels, nodes, organizations, users, and sorting servers. Users are registered in the organization. The organization associates users with corresponding trading nodes, and assigns trading nodes to different channels according to transaction types. Each channel is configured with a corresponding sorting server or sorting server cluster. The forwarding server forwards the component operation request to the corresponding component operation server according to the component type indicated in the plaintext, so that the component operation server performs operation processing on the corresponding component.

S204: The current component operation server operates on the current component in the distributed system according to the component operation request to obtain the first component operation result.

The operations on the current component include at least one of new addition of components, exit of components, suspension of components, recovery of components, query of configuration information of components, and change of configuration information of components. For example, the query of the component status, wherein the state of the component includes an initial state, an active state, a stop state, and an exit state, the initial state refers to the component being initialized and has not been activated, and the active state means that the component is activated to participate in the transaction request execution; It means that the component temporarily stops the service. The exit state means that the component exits the system, and the exited component is added to the system again, and then needs to be reinitialized.

If the current component operation server is a channel operation server, the channel operation server can support channel addition, channel exit, channel stop, and channel recovery, wherein the channel stop refers to the channel stop service, and the channel recovery refers to already The service stop channel is re-serviced. The configuration information of the channel includes the name, number, node list, sorting server, user list, and status. Therefore, the channel operation server also supports querying the channel number based on the channel name, and querying the status of the channel based on the channel name.

Current components can include nodes, channels, users, organizations, and sequencing servers in a distributed system.

If the current component operation server is a node operation server, the node operation server can support node addition, node exit, node stop, and node recovery. The configuration information of the node includes the number, name, status, node IP address and port number, event name, event IP address and port number, organization name, channel list, and so on. Therefore, the node operation server also supports querying the node number based on the node's IP address and port, querying the node status based on the node's IP address and port, and the channel list of the channel to which the node is added.

If the current component operation server is an organization operation server, the organization operation server can support the addition of the organization, the exit of the organization, the stop of the organization, and the recovery of the organization. The configuration information of the organization may include a number, a name, a node list, a user list, a status, a mapping relationship between the node and the user, etc., so the organization operation server may also support the organization number query based on the organization name, the organization status query, and the like.

If the current component operation server is a user operation server, the user operation server can support user addition, user exit, user stop, and user recovery. And the user's configuration information may include a number, a name, a status, an organization name, an organization user name, a user key, and a user certificate. Therefore, the user operation server can also support the query based on the organization user name (character combination of the organization name and the user name), and can also query the status based on the user name and the organization name.

If the current component operation server is a sort server operation server, the sort server operation server can support the addition of the sort server, the exit of the sort server, the stop of the sort server, and the recovery of the sort server. And the configuration information of the sorting server may include a number, a name, a status, an IP address of the sorting server, and a port. Therefore, the sorting server operation server can also support the number and status of the sorting server based on the IP address and port query of the sorting server.

S206: The current component operation server returns the first component operation result to the forwarding server, so that the forwarding server sends the first component operation result to the system client.

The current component operation server returns the first component operation result to the forwarding server, so that the forwarding server can store the first component operation result, and then send the first component operation result to the system client, and the system client forwards the result to the system client. User, etc.

In the above distributed system management method, after receiving the component operation request, the forwarding server forwards the component management request to the corresponding current component operation server according to the component type, so that the current component operation server can perform operations on the current component by introducing forwarding. The server and the component operation server operate on the component, and no need to manually change the system after the system is shut down, saving time and improving efficiency, and reducing the cost of the user because the research and development personnel are no longer required to participate.

In one embodiment, after the step of the current component operation server operating the current component according to the component operation request to obtain the first component operation result, the method may further include: the current component operation server sending the first component operation result to the associated component operation server. So that the associated component operation server operates on the associated component associated with the current component according to the first component operation result to obtain the second component operation result, and returns the second operation result to the forwarding server; the forwarding server sends the second component operation result to System client.

Since there are multiple components in the system, each component is organically connected. When one component changes, other components need to change accordingly. Therefore, if the current component operation server sends the first component operation result to the associated component operation server, the associated component operation server adjusts the associated component according to the first component operation result, for example, adjusting the configuration information of the management component, etc., and managing the component operation. The server returns the operation result of the management component, that is, the operation result of the second component to the forwarding server, and is stored by the forwarding server, and then sent to the system client, so that the user who uses the system client can timely know the status of the current component of the system. Wait.

In the above embodiment, when a component in the system changes, other components associated with the component also change accordingly, so that the changes between the components are organically linked, and there is no need to manually adjust other components according to changes of one component. Components that increase the efficiency of component changes, system scalability, and system integrity.

Referring to FIG. 3, FIG. 3 is a schematic diagram of component association in an embodiment, including a channel, a node, an organization, a user, and a sorting server. Channels are associated with sorting servers, nodes, and user credentials, nodes are associated with channels and organizations, and organizations are associated with users. The channel changes include the addition of the channel, the exit of the existing channel, the stop of the existing channel, the recovery of the stopped channel, and the change of the channel name. After the channel name changes, the new channel name will be used as the unique identifier of the channel. The status changes accordingly according to the channel change; and when the channel name changes, the channel list in the configuration information of the nodes in the channel changes accordingly. The associated components of the channel include nodes, users, and sorting servers. Changes in nodes, users, and sorting servers all trigger changes in the configuration information of the channel. For details, see below.

In one of the embodiments, when the current component operation server is a node operation server, the associated component operation server is an organization operation server and a channel operation server.

Specifically, the change of the node includes the addition of the node, the exit of the existing node, the stop of the existing node, the restoration of the existing node, the change of the name of the node, the change of the IP address and port of the node, and the event name of the node. Changes, changes in the IP address and port of the node, changes in the organization name of the node, and so on. The state of the node changes accordingly according to the change of the change.

A change in a node triggers a change in the configuration information of the physical organization to which it belongs and a change in the configuration information of the logically associated channel. When the system client submits the changed organization operation request of the above node, the message packet needs to provide not only the configuration information of the node but also the list of channel names of the channel to which the node belongs.

When the node change is a new node and the organization name of the newly added node is new, the node operation server notifies the organization operation server, the organization operation server creates a new organization, and assigns a new user list to the organization, and organizes The operation server assigns a user to the newly added node and establishes a mapping relationship between the newly added node and the user. When the node change is a new node and the channel name of the newly added node is new, the node operation server notifies the channel operation server, the channel operation server creates a new channel, and adds the newly added node to the new channel. At the same time, the user list of the channel is updated according to the user corresponding to the node.

When the change of the node is the exit of the existing node or the stop of the existing node, the node operation server notifies the organization operation server and the channel operation server, and the organization operation server will list the node of the configuration information of the organization to which the changed node belongs. The changed node is deleted, and the mapping relationship between the node and the user is updated; the channel operation server deletes the changed node from the node list of the channel configuration information of the changed node.

When the change of the node is the recovery of the stopped node, the node operation server notifies the organization operation server and the channel operation server, and the organization operation server adds the changed node to the node list of the configuration information of the organization to which the changed node belongs, And updating the mapping relationship between the node and the user, and the channel operation server adds the changed node to the node list of the configuration information of the channel to which the changed node belongs.

When the change of the node is the change of the IP address and port of the node, the node operation server notifies the organization operation server and the channel operation server, and the organization operation server updates the identifier of the node in the organization associated with the changed node correspondingly, the channel The operation server also updates the identifier of the node in the channel associated with the changed node correspondingly. Changes in the node's IP address and port, as well as changes in the IP address and port of the node's time, trigger a reconnection of the channel to that node.

When the other configuration information of the node changes, such as the change of the event name of the node and the change of the organization name of the node, the organization operation server and the channel operation server may decide whether to perform processing according to requirements, and the default situation is not performed. Processed.

In the above embodiment, if the current operation server is a node operation server, the associated operation server is a channel operation server and an organization operation server, so that the channel operation server and the organization operation server are corresponding to the first operation result of the node operation server. The channel and organization operate to realize the dynamic management of system components, improve the unity and integrity of the system, establish the internal relationship between system components, and improve the robustness and stability of the system.

In one of the embodiments, the current component operation server operates the server for the user, and the associated component operation server is an organization operation server.

Specifically, the user's changes include the user's new addition, the exit of the existing user, the stop of the existing user, the recovery of the stopped user, and the change of the user name, the change of the user organization name, the change of the user organization name, Changes in the user's key and certificate, the user's status will change accordingly according to the user's changes.

When the user's change is a new user and the user organization name in the user configuration information is added, the user operation server notifies the organization operation server, the organization operation server creates a new organization, and attributes the user to the new one. Organization.

When the user's change is the exit of the existing user or the stop of the existing user, the user operation server notifies the organization operation server, and the organization operation server updates the user list of the configuration information of the corresponding organization, and corresponds to the changed user. After the node allocates a new user, the node and the user's mapping relationship table are updated, and the organization operation server notifies the corresponding channel operation server to update the user list of the corresponding channel.

When the user's change is the recovery of the existing user, the user operation server first sets the user to be available, and then notifies the organization operation server, and the organization operation server adds the change user to the user list of the corresponding organization.

When the user's change is that the user name changes, the user operation server updates the user's organization user name; when the user's change is that the user's organization name changes, the user operates the server to update the user's organization user name; when the user changes When the user name of the user changes, the user name is changed or the name of the organization name is changed by comparing the original organization user name, and the organization name is changed. Then the user operates the server to update the user name of the user. When the username changes, the user operates the server to update the user's username. In the above two changes, the change of the user's organization name will adjust the current user to be used by other organizations, and accordingly the user operation server will notify the organization operation server to adjust the user-related information of the old organization and the new organization, and The organization operation server adjusts the user corresponding to the node, and the organization operation server notifies the channel operation server, and the channel operation server changes the user list.

When the user's change is a change of the user's key or certificate, the user operation server notifies the channel operation server and the organization operation server, and the channel operation server and the organization operation server update the corresponding key or certificate.

In the above embodiment, if the current operation server is a user operation server, the associated operation server is an organization operation server, so that the organization operation server operates the corresponding organization according to the first operation result of the user operation server, and implements the system component. Dynamic management improves the unity and integrity of the system, establishes the internal relationship between system components, and improves the robustness and stability of the system.

In one of the embodiments, the current component operation server is an organization operation server, and the associated component operation server is a node operation server and a user operation server.

Organizational changes include the addition of an organization, the withdrawal of an existing organization, the cessation of an existing organization, the restoration of an organization that has ceased, and the change in the name of the organization. The change in the name of the organization can be seen in detail above.

When the organization's change is the addition of the organization, it means that the system will add a new organization. Therefore, the nodes and users of the newly added organization need to be configured accordingly. The organization operation server will notify the node operation server to add nodes, and notify the user to increase the operation server. user.

When the organization's change is the exit of an existing organization or the stop of an existing organization, the organization operation server will update all nodes and users in the organization; for the exit of the existing organization, the organization operation server will notify the corresponding node to operate the server and user. The state of the operation server update node is the exit state, and the state of the update user is the exit state; for the stop of the existing organization, the organization operation server notifies the corresponding node operation server and the user operation server to update the state of the node to the stop state, and update the state of the user. The stop operation state; and the node operation server will send a message to the associated channel operation server, the channel operation server will remove the relevant node in the node list of the channel, and the organization operation server will send a message to the channel operation server, and the channel operation server will Remove the relevant user certificate from the list of user certificates for the associated channel.

When the change of the organization is the recovery of the stopped organization, the organization operation server notifies the node operation server to update the state of the corresponding node to the active state, and the node operation server notifies the channel operation server, and the channel operation server lists the node of the channel in the node. The related node is added; the organization operation server is notified to notify the user that the operation server updates the user's status to the active state, and the organization operation server notifies the channel operation server, and the channel operation server adds the relevant user certificate to the user certificate list of the channel to which the user belongs.

In the above embodiment, the current component operation server is an organization operation server, and the associated component operation server is a node operation server and a user operation server, so that the node operation server and the user operation server are corresponding to the first operation result of the organization operation server. Users and nodes operate to realize dynamic management of system components, improve system uniformity and integrity, establish internal links between system components, and improve system robustness and stability.

In one of the embodiments, the current component operation server is a sort server operation server, and the associated component operation server is a channel operation server.

The changes in the sorting server include the addition of the sorting server, the exit of the existing sorting server, the stop of the existing sorting server, the recovery of the stopped sorting server, the change of the name of the sorting server, the IP address of the sorting server, and the change of the port. .

When the change of the sorting server is the recovery of the sorting server's new or sorting server, the sorting server operation server configures the name, IP address, and port for the new sorting server, and notifies the corresponding channel operation server.

When the change of the sorting server is the exit of the existing sorting server or the stop of the existing sorting server, the sorting server operation server updates the state of the changing sorting server to the exit state or the stop state, and sends a message to the channel operation server, the channel The operation server changes the sorting server list of the configuration information of the associated channel.

When the change of the sorting server is a change of the IP address and the port, the sorting server operates the server to change the IP address and port of the corresponding sorting server, and then notifies the channel operating server that the channel operating server replaces the old IP address and port with the old IP address and port.

In the above embodiment, the current component operation server is a sorting server operation server, and the associated component operation server is a channel operation server, so that the channel operation server operates the corresponding channel according to the first operation result of the sorting server operation server, and realizes The dynamic management of system components improves the uniformity and integrity of the system, establishes the internal relationship between system components, and improves the robustness and stability of the system.

Please continue to refer to Figure 3, where the channel can be uniquely identified by the channel name or channel number. The channel contains one or more nodes, one or more user certificates, and one or more sorting servers, where the default state is A sorting server, multiple sorting servers are used to determine the sorting result after sorting the server consensus. When a channel-based transaction request is executed, the channel sends a transaction request to each node in the channel, and executes a transaction request through the node, and after the transaction request is completed, the node returns the preliminary transaction result to the channel, and the channel is based on the preliminary transaction. The result is the target transaction result, and the target transaction result is sent to the sorting server, which is sorted and stored by the sorting server. The user certificate list of the channel refers to the user certificate list of the user of the organization to which the node belongs in the channel. When the channel communicates with the node in the channel, for example, sending a transaction request message, the public key in the user certificate is selected for the message. The field is encrypted and tagged with the channel's own private key, which sends the public key as part of the message to the node.

A node is uniquely identified by the IP address of the node and the number of the port or node. The node is physically attributed to an organization, logically associated with one or more channels, ie, one node can be used by one or more channels to perform Transaction request. After receiving the packet of the channel, the node checks the packet in the channel, and decrypts the field of the agreed message with the user private key corresponding to the node, and then executes the corresponding transaction request.

The user is uniquely identified by the organization user name or user number. The user belongs to an organization. The user in one organization can correspond to one or more nodes in the organization, that is, the user private key can be one or more in the organization. Node ownership, by default, the private key of a user of the organization is owned by a node in the organization.

The organization is based on the organization name or the number of the organization. The organization contains nodes and users. The organization assigns one user to each node. The users corresponding to each node can be the same or different. The organization will establish nodes and The mapping relationship between users.

The sorting server is uniquely identified by the IP address of the sorting server and the port or sorting server number. The sorting server provides the channel with the sorting and storage function of the target transaction result.

Please refer to FIG. 4. FIG. 4 is a flowchart of a transaction request processing step according to one or more embodiments. The transaction request processing step may include:

S402: The request response server receives the transaction request sent by the system client, and forwards the received transaction request to the request server.

Specifically, the system client can receive the transaction request and forward the transaction request to the request response server, the request response server generates a number regarding the transaction request, and forwards the transaction request and number to the request server.

S404: The requesting server acquires the state of the component corresponding to the transaction request, and when the state of the component is the available state, the component transaction result is processed by the component to obtain the target transaction result.

Specifically, the request server parses the type of the transaction request according to the transaction request sent by the response server, and selects an appropriate channel according to the type of the transaction request; and the request server can read the channel and the channel by communicating with the channel operation server or the forwarding server. Relevant component information and status, such as node information and status; if the status of the channel and related components is available, ie active, then the transaction request is forwarded to the node in the channel for execution, the nodes in the channel The transaction request is processed to obtain a preliminary transaction result, and the preliminary transaction result is returned to the channel. The channel obtains the target transaction result based on the preliminary transaction result and the consensus algorithm strategy, and returns the target transaction result to the request server, wherein after the channel obtains the target transaction result, the target transaction result may be sent to the corresponding sorting server for processing, sorting. The server may sort the target transaction result by time, store the sorted target transaction result, the node may synchronously sort the target transaction result in the server, and the sorting server may actively send the sorted target transaction result to the request. server.

S406: After requesting the server to send the target transaction result to the request response server, the request response server sends the target transaction result to the system client.

Specifically, after the requesting server obtains the target transaction result, the target transaction result is sent to the request response server, and the target response result is returned to the system client by the request response server.

In the above embodiment, the transaction request is processed by introducing the request response server and the request server, and the transaction request is processed separately from the component operation request without affecting each other, thereby improving the robustness and stability of the system.

In one embodiment, referring to FIG. 5, FIG. 5 is a flowchart of a transaction request processing step and a component operation request processing step in an embodiment; after the step of requesting the processor to acquire the state of the component corresponding to the transaction request, The method includes: the requesting server receives the first component operation result and the second component operation result; and when the component state is the available state, the step of processing the transaction request by the component to obtain the target transaction result, including: the first component operation result and the first component The result of the two component operation obtains the available components after the operation, and processes the transaction request through the available components to obtain the target transaction result.

Specifically, the processing directly involved in the processing of the transaction request includes a channel, a node, a user, and a sorting server, and the change of the organization triggers the change of the node and the user, thereby indirectly affecting the execution of the request, wherein the user's change triggers the The change of the user certificate in the associated channel and the change of the user private key of the associated node, the change of the node triggers the change of the node list of the channel, and the change of the sorting server triggers the change of the list of the sorting server of the associated channel, After the current component operation server operates on the current component to obtain the first component operation result and the associated component operation server operates the associated component to obtain the second component operation result, the current component operation server and the associated component operation server may directly directly use the first component. The operation result and the second component operation result are sent to the request server, or are forwarded to the request server by the channel operation server, or forwarded to the request server by the forwarding server, and the request server receives the first component operation result and the second component operation node. After accordingly acquired available components, and processes the transaction request by the available components to obtain the target transaction result.

The requesting server performs the transaction request by using the channel service as the main body. When the component operation result is received, if the component operation result includes the channel change, for example, the component operation result includes the channel addition, the newly added channel is executed and executed. The channel of the transaction request is not associated and therefore has no effect on the transaction request. If the component operation result includes the exit of the channel, the channel service of the channel is directly terminated. If the component operation result includes the stop of the channel, the channel service of the channel is directly stopped. If the component operation result includes the recovery of the stopped channel, the channel service of the channel is directly replied, and the processing of the transaction request is not affected.

If the component operation result includes a change in the channel name, it has no effect on the transaction request being executed, and when the channel receives a new transaction request, it is allocated according to the new channel name.

If the component operation result includes a change in the node list of the channel, for example, when there is a new node in the node list, when the transaction request has not been sent to the node in the channel for execution, the transaction request is sent to the new transaction node if the transaction When the request has been sent to an existing node in the channel, the new node will not participate in the execution of the transaction request, and the existing node in the channel continues to execute the current transaction request; when there is a decrease in the node list in the channel, If the current transaction request has been sent to the node in the channel, that is, it is also sent to the reduced node, the current transaction request will continue. At this time, the communication timeout processing between the channel and the node is processed accordingly, that is, regardless of Whether the reduced nodes have feedback will not affect the execution and processing results of the transaction request. If the component operation result includes a change of the user list of the channel, since the channel encrypts the key segment of the transaction request by using the public key in the user certificate corresponding to the node, the node receiving the transaction request decrypts through the corresponding user private key. The user and the node belong to the same organization. Therefore, for the change of the user list, refer to the change of the node list in the above, and details are not described herein again.

If the result of the component operation includes the change of the sorting server, since the channel server only needs n/2+1 of the number of nodes (n represents the number of nodes), the execution result of the current transaction request is consistent; Otherwise, the transaction request execution is considered to have failed. The sorting server list in the channel is used to achieve consistency in the sorting service. It also requires the number of m/2+1 (m represents the number of sorting servers) to be consistent, and the transaction request execution result is consistent; otherwise, the transaction request execution fails; In the case where the channel uses a single sorting server, for a single sorting server, if the sorting service is in progress, the sorting server exits or stops, the system assigns a new sorting server to the channel service, and the channel service is reordered; the sorting server is added. Or recovery, re-provisioned by the requesting processor, does not affect the execution of the current request.

In the above embodiment, when there is a component operation result in the transaction request processing process, the request server correspondingly executes the transaction request according to the component operation result, and the transaction request processing is not suspended or lost due to the operation of the component, thereby improving the stability of the system. .

In one embodiment, the method may further include: when the requesting server is processing the transaction request, after the requesting server processes the transaction request by the component to obtain the target transaction result, the current component operation server performs the current component according to the component operation request. The operation obtains the result of the first component operation.

Specifically, when the request server is processing the transaction request, when the component operation request occurs, the system may first suspend execution of the component operation request, first process the transaction request to obtain the target transaction result, and then perform the current component according to the component operation request. The operation gets the result of the first component operation, which prevents the component operation request from affecting the transaction request.

In the above embodiment, when there is a component operation request in the transaction request processing process, the execution of the component operation request may be suspended first, that is, the transaction request is processed first, and the component operation request is processed after the transaction request processing is completed, thereby ensuring that the component operation request is processed. The normal processing of transaction requests improves the stability of the system.

It should be understood that although the steps in the flowcharts of FIGS. 2, 4, and 5 are sequentially displayed in accordance with the indication of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIGS. 2, 4, and 5 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times. The order of execution of the sub-steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of the sub-steps or stages of the other steps or other steps.

With continued reference to FIG. 1, FIG. 1 illustrates an operating system of a distributed system including a forwarding server and a current component operation server.

The forwarding server is configured to forward the received component operation request to the current component operation server according to the component type.

The current component operation server is configured to operate the current component in the distributed system according to the component operation request to obtain the first component operation result; and return the first component operation result to the forwarding server, so that the forwarding server sends the first component operation result.

In one of the embodiments, the component operation request includes at least one of a component addition request, a component exit request, a component stop request, a component recovery request, a component configuration information query request, or a component configuration information change request.

In one embodiment, the current component operation server is further configured to send the first component operation result to the associated component operation server, so that the associated component operation server operates the associated component associated with the current component according to the first component operation result. After the result of the two component operations, the second operation result is returned to the forwarding server.

The forwarding server is also used to send the second component operation result to the system client.

In one of the embodiments, the system further includes a request response server and a request server.

The request response server is configured to receive a transaction request sent by the system client and forward the received transaction request to the request server.

The request server is configured to obtain the state of the component corresponding to the transaction request, and when the state of the component is available, the transaction request is processed by the component to obtain the target transaction result, and the target transaction result is sent to the request response server.

The request response server is also used to send the target transaction result to the system client.

In one embodiment, the requesting server is further configured to: after acquiring the state of the component corresponding to the transaction request, receive the first component operation result and the second component operation result; and according to the first component operation result and the second component operation result Get the available components after the operation, and process the transaction request through the available components to get the target transaction result.

In one embodiment, the current component operation server is further configured to: when the request server is processing the transaction request, after the request server processes the transaction request through the component to obtain the target transaction result, and the current component is operated according to the component operation request. The first component operation result.

One of ordinary skill in the art can understand that all or part of the process of implementing the above embodiments can be completed by computer readable instructions, which can be stored in a non-volatile computer. The readable storage medium, which when executed, may include the flow of an embodiment of the methods as described above. Any reference to a memory, storage, database or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A distributed system operation method includes:

The current component operation server receives the component operation request forwarded by the forwarding server according to the component type;

The current component operation server operates on the current component in the distributed system according to the component operation request to obtain a first component operation result; and

The current component operation server returns the first component operation result to the forwarding server, so that the forwarding server sends the first component operation result to the system client.
The method according to claim 1, wherein the component operation request comprises at least a component addition request, a component exit request, a component stop request, a component recovery request, a component configuration information query request, or a component configuration information change request. One.
The method according to claim 1 or 2, wherein after the current component operation server operates the current component according to the component operation request to obtain the first component operation result, the method further includes:

The current component operation server sends the first component operation result to the associated component operation server, so that the associated component operation server operates the associated component associated with the current component according to the first component operation result to obtain a second component operation result. Returning the second operation result to the forwarding server; and

The forwarding server sends the second component operation result to the system client.
The method according to claim 3, wherein when the current component operation server is a node operation server, the associated component operation server is an organization operation server and a channel operation server.
The method according to claim 3, wherein the current component operation server is a user operation server, and the associated component operation server is an organization operation server.
The method according to claim 3, wherein the current component operation server is an organization operation server, and the associated component operation server is a node operation server and a user operation server.
The method of claim 3, wherein the method further comprises:

The request response server receives the transaction request sent by the system client, and forwards the received transaction request to the request server;

Requesting a server to acquire a state of a component corresponding to the transaction request, and processing the transaction request by the component to obtain a target transaction result when the state of the component is an available state; and

After the requesting server sends the target transaction result to the request response server, the request response server sends the target transaction result to the system client.
The method according to claim 7, wherein after the requesting processor acquires the state of the component corresponding to the transaction request, the method further includes:

The requesting server receives the first component operation result and the second component operation result;

When the status of the component is in an available state, the transaction request is processed by the component to obtain a target transaction result, including:

Obtaining the available components after the operation according to the first component operation result and the second component operation result, and processing the transaction request by the available component to obtain a target transaction result.
The method of claim 7, wherein the method further comprises:

When the requesting server is processing the transaction request, after the requesting server processes the transaction request by the component to obtain the target transaction result, the current component operation server performs the current component according to the component operation request. The operation obtains the result of the first component operation.
A distributed system operating system, including a forwarding server and a current component operation server;

The forwarding server is configured to forward the received component operation request to the current component operation server according to the component type;

The current component operation server is configured to operate the current component in the distributed operating system according to the component operation request to obtain a first component operation result; and return the first component operation result to the forwarding server, so that The forwarding server sends the first component operation result.
The system according to claim 10, wherein the component operation request comprises at least a component addition request, a component exit request, a component stop request, a component recovery request, a component configuration information query request, or a component configuration information change request. One.
The system according to claim 10 or 11, wherein the current component operation server is further configured to send the first component operation result to an associated component operation server, so that the associated component operation server is according to the first The component operation result is performed on the associated component associated with the current component to obtain a second component operation result, and the second operation result is returned to the forwarding server;

The forwarding server is further configured to send the second component operation result to the system client.
The system according to claim 12, wherein when the current component operation server is a node operation server, the associated component operation server is an organization operation server and a channel operation server.
The system according to claim 12, wherein the current component operation server is a user operation server, and the associated component operation server is an organization operation server.
The system according to claim 12, wherein the current component operation server is an organization operation server, and the associated component operation server is a node operation server and a user operation server.
The system of claim 12, wherein the system further comprises a request response server and a request server;

The request response server is configured to receive a transaction request sent by the system client, and forward the received transaction request to a request server;

The request server is configured to acquire a state of a component corresponding to the transaction request, and when the state of the component is an available state, process the transaction request by the component to obtain a target transaction result, and the target is Transaction results are sent to the request response server;

The request response server is further configured to send the target transaction result to the system client.
The system according to claim 16, wherein the requesting server is further configured to receive the first component operation result and the second component operation result after acquiring a state of a component corresponding to the transaction request And obtaining an available component after the operation according to the first component operation result and the second component operation result, and processing the transaction request by the available component to obtain a target transaction result.
The system according to claim 16, wherein said current component operation server is further configured to process said transaction request by said component at said request server when said request server is processing a transaction request After the target transaction result is obtained, the current component is operated according to the component operation request to obtain the first component operation result.