WO2022021850A1 - 一种服务实例部署方法、装置、电子设备和存储介质 - Google Patents

一种服务实例部署方法、装置、电子设备和存储介质 Download PDF

Info

Publication number
WO2022021850A1
WO2022021850A1 PCT/CN2021/076872 CN2021076872W WO2022021850A1 WO 2022021850 A1 WO2022021850 A1 WO 2022021850A1 CN 2021076872 W CN2021076872 W CN 2021076872W WO 2022021850 A1 WO2022021850 A1 WO 2022021850A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
service instance
monitoring
regionserver
hbase
Prior art date
Application number
PCT/CN2021/076872
Other languages
English (en)
French (fr)
Inventor
申胜利
亓开元
Original Assignee
苏州浪潮智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 苏州浪潮智能科技有限公司 filed Critical 苏州浪潮智能科技有限公司
Priority to US18/005,945 priority Critical patent/US12020084B2/en
Publication of WO2022021850A1 publication Critical patent/WO2022021850A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G06F9/45516—Runtime code conversion or optimisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory

Definitions

  • the present application relates to the field of computer technologies, and more particularly, to a service instance deployment method, apparatus, electronic device, and computer-readable storage medium.
  • the RegionServer (regional service) of HBASE (Hadoop Database, a highly reliable, high-performance, column-oriented, scalable distributed storage system) provides specific data query and insertion, manages the region (region) where data is stored, and provides access to memory Demand is relatively high.
  • HBASE Hadoop Database
  • the Ambari management platform can only install one RegionServer instance on one node. Under the dedicated HBASE physical cluster, physical resources cannot be fully and effectively utilized.
  • the purpose of this application is to provide a service instance deployment method and device, an electronic device and a computer-readable storage medium, which can deploy multiple service instances on the same physical node, fully utilize the resources of one physical node, and improve the HBASE cluster stability.
  • the present application provides a service instance deployment method, including:
  • each of the processes is a RegionServer component for executing a service instance
  • each described service instance For each described service instance, assign a sign character, and based on the sign character, for each described service instance assigning a corresponding port; Wherein, each described service instance sign character is as the system parameter of the corresponding process;
  • Corresponding log files and pid files are created for each of the service instances based on the flag characters.
  • assigning a corresponding port to each of the service instances based on the flag characters includes:
  • a command line corresponding to each of the service instances is added at the main function parameter position based on the flag characters, so as to override the port configuration of HBASE itself, and assign a corresponding port to each of the service instances.
  • a command line corresponding to each service instance is added in the setting position of the JAVA virtual machine, so that each service instance logo character can be used as a system parameter of the corresponding process.
  • the roles corresponding to the service instance include all The RegionServer component corresponding to the service instance described above;
  • a corresponding operation execution script is created for each of the service instances based on the flag characters, so as to execute the corresponding operation execution script according to the operation execution sequence.
  • An alarm module corresponding to each service instance is added to the alarm configuration file of the HBASE service of ambari based on the flag characters, so that each alarm module detects whether the port corresponding to the service instance is detected every first preset time. is used, and alerts the service instance corresponding to the unused port.
  • a monitoring module corresponding to each service instance is added to the monitoring indicator configuration file of the HBASE service of ambari based on the flag characters, so that each monitoring module obtains all the information of the corresponding service instance from the monitoring component monitoring indicators;
  • a monitoring window corresponding to each service instance is added to the window tool configuration file of the HBASE service of ambari, so that each monitoring window displays all the monitoring indicators of the corresponding service instance.
  • a service instance deployment device including:
  • the first creation module is used to create multiple processes in the target physical node; wherein, each described process is a RegionServer component for executing a service instance;
  • an allocation module configured to allocate a logo character to each of the service instances, and to allocate a corresponding port to each of the service instances based on the logo character; wherein, each of the service instance logo characters is used as a system of a corresponding process parameter;
  • the second creation module is configured to create a corresponding log file and a pid file for each of the service instances based on the flag characters.
  • an electronic device including:
  • the processor is configured to implement the steps of the above-mentioned service instance deployment method when executing the computer program.
  • the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, implements the steps of the above-mentioned service instance deployment method.
  • a service instance deployment method includes: creating multiple processes in a target physical node; wherein each of the processes is a RegionServer component for executing a service instance; The service instance assigns a flag character, and assigns a corresponding port to each of the service instances based on the flag character; wherein, each of the service instance flag characters is used as a system parameter of the corresponding process; based on the flag characters: Each instance of the service creates a corresponding log file and pid file.
  • the service instance deployment method provided in this application realizes that the RegionServer of HBASE deploys multiple instances on the same physical node, which can reduce the pressure of a single RegionServer under the condition of the same number of regions, and can also reduce Juliet under the same total memory usage.
  • the occurrence of the pause improves the stability of the HBASE cluster, makes more full use of the physical resources of the cluster, deploys more RegionServer instances without physical expansion, and reduces the cost of expansion in some scenarios.
  • the present application also discloses an apparatus for deploying a service instance, an electronic device, and a computer-readable storage medium, which can also achieve the above technical effects.
  • FIG. 1 is a flowchart of a method for deploying a service instance according to an exemplary embodiment
  • FIG. 2 is a structural diagram of an HBASE cluster according to an exemplary embodiment
  • FIG. 3 is a structural diagram of an apparatus for deploying a service instance according to an exemplary embodiment
  • FIG. 4 is a structural diagram of an electronic device according to an exemplary embodiment.
  • the embodiment of the present application discloses a service instance deployment method, which deploys multiple service instances on the same physical node, fully utilizes the resources of one physical node, and improves the stability of the HBASE cluster.
  • FIG. 1 a flowchart of a method for deploying a service instance according to an exemplary embodiment, as shown in FIG. 1 , includes:
  • S101 Create multiple processes in the target physical node; wherein, each of the processes is a RegionServer component for executing a service instance;
  • the executive body of this implementation is the management node of the HBASE cluster, and the purpose is to deploy multiple service instances on the same physical node.
  • multiple processes are created in the same target physical node, and each process is a RegionServer component, which is used to execute a service instance (ie, RegionServer instance), that is, to respond to user's read and write requests, and the service instance is HBASE It maintains write-ahead logs, read-write caches, and manages multiple regions.
  • S102 Allocate a flag character to each of the service instances, and assign a corresponding port to each of the service instances based on the flag characters; wherein, each of the service instance flag characters is used as a system parameter of a corresponding process;
  • the execution mode of HBASE itself is modified so that it can recognize the logo character of the service instance in the execution command when operating the RegionServer instance.
  • the logo character of each service instance can be realized by adding a suffix to the parameter RegionServer, Based on the flag character, the corresponding RegionServer instance can be started, and according to the different flag characters, the corresponding system parameters and port configurations can be added for different service instances when starting the JAVA process.
  • the step of allocating a corresponding port to each of the service instances based on the flag characters includes: adding a command line corresponding to each of the service instances at the main function parameter position based on the flag characters, so as to cover HBASE's own Port configuration, assigning a corresponding port to each of the service instances.
  • This embodiment further includes: adding a command line corresponding to each service instance in the setting position of the JAVA virtual machine, so that each service instance logo character is used as a system parameter of the corresponding process.
  • S103 Create a corresponding log file and pid file for each of the service instances based on the flag characters.
  • corresponding log files and pid (process identifier, Process Identification) files are created for different service instances.
  • the Pid file is a text file with only one line in its content, recording the ID of its corresponding process.
  • the files are named based on their logo characters for use by the corresponding process, so as to deploy multiple service instances on the target physical node.
  • the HBASE cluster includes two physical nodes, and each physical node deploys three Service instances, the identifiers of each service instance are RegionServer, RegionServer1 and RegionServer2 respectively.
  • the Master (host) in the management node is connected to each service instance in each physical node respectively.
  • this embodiment further includes: adding the RegionServer component corresponding to each service instance in the meta-information configuration file of ambari's HBASE service based on the flag characters;
  • the role corresponding to each service instance is added to the role operation sequence file of the service, and the execution sequence of the operation corresponding to each role is configured; wherein, the role corresponding to the service instance includes the RegionServer component corresponding to the service instance; based on The flag character creates a corresponding operation execution script for each of the service instances, so as to execute the corresponding operation execution script according to the operation execution sequence.
  • transform the background execution steps corresponding to the page operations of the HBASE service RegionServer component of ambari (a web-based tool that supports provisioning, management and monitoring of Apache Hadoop clusters), so that it can execute newly added files with different
  • the operations of the suffixed RegionServer components such as start, stop, restart, enable safe mode and auto-restart, and follow the correct sequence when operating the HBASE service as a whole.
  • the newly added RegionServer components with different suffixes will perform the steps of operating the RegionServer components in the modified ambari. In the modified steps, you need to execute the steps after enabling security.
  • RegionServer The part and other parts common to RegionServer, such as user group permission check, still use the execution process of the original RegionServer, and finally call the part of the execution command of HBASE itself, such as start, stop, restart, etc., when using HBASE itself to execute the command. Add the suffix here to the parameter RegionServer.
  • the newly added HBASE-RegionServer roles with different suffixes will be executed in sequence at the same level as HBASE-RegionServer.
  • the service instance deployment method provided by the embodiment of the present application realizes that the RegionServer of HBASE deploys multiple instances on the same physical node, which can reduce the pressure of a single RegionServer under the condition of the same number of regions, and can also use the same total memory usage under the condition of It reduces the occurrence of Juliet pauses, improves the stability of the HBASE cluster, and can more fully utilize the physical resources of the cluster, deploy more RegionServer instances without physical expansion, and reduce the cost of expansion in some scenarios.
  • the method further includes: adding an alarm module corresponding to each service instance in the alarm configuration file of the HBASE service of ambari based on the flag characters, so that each of the The alarm module detects whether the port corresponding to the service instance is used every first preset time, and alarms the service instance corresponding to the unused port.
  • the newly added HBASE_RegionServer module with different suffixes in the warning configuration file in the HBASE service configuration directory of ambari namely the alarm module, will make ambari detect the corresponding node with the suffix component at intervals of time. If the port cannot be detected, the red warning message of HBASE_RegionServer with the suffix will be displayed on the page, and the error content will be displayed.
  • this embodiment further includes: acquiring the alarm content of each of the alarm modules every second preset time, determining an alarm node including an alarm service example, and counting the number of all the alarm nodes.
  • the newly added sub-module with a suffix will enable ambari to detect the monitoring content of the above-mentioned module at intervals, and when the above-mentioned module alarms, count the total nodes with the suffix and the total number of components. Number of alarm nodes.
  • an alarm can be triggered after the newly added RegionServer component with a suffix on some nodes goes down, and the number of normal and abnormal ones can be displayed.
  • the method further includes: adding a monitoring indicator corresponding to each service instance in the monitoring component of ambari based on the sign character, so that the monitoring component can monitor each service instance by the monitoring component. All the monitoring indicators of the service instance are monitored; based on the flag characters, add the monitoring module corresponding to each of the service instances in the monitoring indicator configuration file of the HBASE service of ambari, so that each of the monitoring modules can be Obtain all the monitoring indicators of the corresponding service instance in the monitoring component; add the monitoring window corresponding to each service instance in the window tool configuration file of the HBASE service of ambari based on the flag character, so that each monitoring window Displays all the monitoring metrics for the corresponding service instance.
  • the process of collecting monitoring information in the background of ambari is modified, and according to the sign character of each service instance, the monitoring indicator name of the corresponding process is added with different tags as suffixes to form a new indicator name, which distinguishes the same monitoring of different processes.
  • the content is stored in the backend storage of ambari's monitoring component.
  • the newly added HBASE_RegionServer module with different suffixes is the monitoring module.
  • the terminal stores the monitoring indicator content of the process where the RegionServer components with different suffixes are located.
  • the newly added monitoring windows with different suffixes display the corresponding monitoring content of the RegionServer components with different suffixes on the page, such as the heat map HBASE Region number and monitoring read and write times, in
  • the name of the monitoring indicator that each monitoring window needs to calculate corresponds to the name of the above-mentioned indicator with a suffix added, so that monitoring windows with different suffixes can reflect the different RegionServer processes where the RegionServer components with different suffixes are located. specific monitoring information. Similar to the above, you can also customize the window to display other monitoring information of different suffix RegionServer components.
  • this embodiment can display various monitoring items of the newly added RegionServer with a suffix, as well as various custom combination monitoring.
  • the service instance deployment may include a background operation module, a page operation module, a warning module and a monitoring module, and the implementation of the above modules may include the following steps:
  • Step 1 Implement the background operation module, transform the execution mode of HBASE itself, so that it can recognize the suffix added to the parameter "RegionServer" in the command executed when operating the original RegionServer instance, and start different RegionServer instances.
  • Step 2 Implement the page operation module, and transform the background execution steps corresponding to the page operation of the RegionServer component of Ambari's HBASE service, so that it can perform the operations of the newly added RegionServer component with different suffixes, such as start, stop, restart, and enable security mode and auto-restart, and follow the correct sequence when operating the HBASE service as a whole.
  • Step 3 Implement the alarm module. After the newly added RegionServer component with a suffix on some nodes goes down, the alarm can be triggered like the original RegionServer. And display the number of normal and abnormal.
  • Step 4 Implement the monitoring module, which can display various monitoring items of the newly added RegionServer with a suffix, as well as various custom combination monitoring, just like the original RegionServer component.
  • the following describes an apparatus for deploying a service instance provided by an embodiment of the present application.
  • the apparatus for deploying a service instance described below and a method for deploying a service instance described above may refer to each other.
  • FIG. 3 a structural diagram of an apparatus for deploying a service instance according to an exemplary embodiment, as shown in FIG. 3, includes:
  • the first creation module 301 is used to create multiple processes in the target physical node; wherein, each of the processes is a RegionServer component for executing a service instance;
  • the allocation module 302 is configured to allocate a logo character to each of the service instances, and allocate a corresponding port to each of the service instances based on the logo character; wherein, each of the service instance logo characters is used as the System parameters;
  • the second creation module 303 is configured to create a corresponding log file and a pid file for each of the service instances based on the flag characters.
  • the service instance deployment device realizes that the RegionServer of HBASE deploys multiple instances on the same physical node, which can reduce the pressure of a single RegionServer under the condition of the same number of regions, and can also use the same total memory usage under the condition of It reduces the occurrence of Juliet pauses, improves the stability of the HBASE cluster, makes more full use of the physical resources of the cluster, deploys more RegionServer instances without physical expansion, and reduces the cost of expansion in some scenarios.
  • the allocation module 302 specifically allocates a logo character to each of the service instances, and adds each of the service instances at the main function parameter position based on the logo character.
  • Corresponding command line in order to override HBASE's own port configuration, assign a module corresponding to the port for each of the service instances.
  • the first adding module is used for adding a command line corresponding to each service instance in the setting position of the JAVA virtual machine, so that each service instance logo character can be used as a system parameter of the corresponding process.
  • the second adding module is used to add the RegionServer component corresponding to each described service instance in the meta-information configuration file of the HBASE service of ambari based on the sign character;
  • the third adding module is used to add the roles corresponding to each of the service instances in the role operation sequence file of the HBASE service of ambari based on the flag characters, and configure the execution order of the operations corresponding to each role; wherein, the The role corresponding to the service instance includes the RegionServer component corresponding to the service instance;
  • the third creation module is configured to create a corresponding operation execution script for each service instance based on the flag characters, so as to execute the corresponding operation execution script according to the operation execution sequence.
  • the fourth adding module is used to add monitoring indicators corresponding to each of the service instances in the monitoring component of ambari based on the flag characters, so that the monitoring component monitors all the monitoring indicators of each of the service instances ;
  • the fifth adding module is used to add a monitoring module corresponding to each of the service instances in the monitoring indicator configuration file of the HBASE service of ambari based on the flag characters, so that each of the monitoring modules obtains the corresponding monitoring module from the monitoring component. All said monitoring metrics of the service instance of ;
  • the sixth adding module is used to add a monitoring window corresponding to each of the service instances in the window tool configuration file of the HBASE service of ambari based on the flag characters, so that each of the monitoring windows displays all the information of the corresponding service instance. monitoring indicators.
  • An alarm module configured to add an alarm module corresponding to each of the service instances in the alarm configuration file of the HBASE service of ambari based on the flag characters, so that each of the alarm modules detects the service every first preset time Whether the port corresponding to the instance is used, and alarm the service instance corresponding to the unused port.
  • the statistics module is configured to acquire the alarm content of each of the alarm modules every second preset time, determine the alarm nodes including the alarm service example, and count the number of all the alarm nodes.
  • the present application further provides an electronic device.
  • a structural diagram of an electronic device 400 provided by an embodiment of the present application may include a processor 11 and a memory 12 .
  • the electronic device 400 may also include one or more of a multimedia component 13 , an input/output (I/O) interface 14 , and a communication component 15 .
  • I/O input/output
  • the processor 11 is used to control the overall operation of the electronic device 400 to complete all or part of the steps in the above-mentioned service instance deployment method.
  • the memory 12 is used to store various types of data to support operation on the electronic device 400 , such data may include, for example, instructions for any application or method operating on the electronic device 400 , and application-related data.
  • the memory 12 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random Access Memory, SRAM for short), electrically erasable programmable read-only memory ( Electrically Erasable Programmable Read-Only Memory (EEPROM for short), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (Read-Only Memory, referred to as ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • the multimedia component 13 may comprise a screen, eg a touch screen.
  • the I/O interface 14 provides an interface between the processor 11 and other interface modules, and the above-mentioned other interface modules may be a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons.
  • the communication component 15 is used for wired or wireless communication between the electronic device 400 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC for short), 2G, 3G or 4G, or one or a combination of them, so the corresponding communication component 15 may include: Wi-Fi module, Bluetooth module, NFC module.
  • the electronic device 400 may be implemented by one or more application-specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), digital signal processors (Digital Signal Processor, DSP for short), digital signal processing devices (Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), controller, microcontroller, microprocessor or other electronic components Implementation is used to execute the above-mentioned service instance deployment method.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • DSP Digital Signal Processor
  • DSP Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • controller microcontroller, microprocessor or other electronic components Implementation is used to execute the above-mentioned service instance deployment method.
  • a computer-readable storage medium including program instructions, the program instructions implementing the steps of the above-mentioned service instance deployment method when executed by a processor.
  • the computer-readable storage medium can be the above-mentioned memory 12 including program instructions, and the above-mentioned program instructions can be executed by the processor 11 of the electronic device 400 to complete the above-mentioned service instance deployment method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

一种服务实例部署方法、装置及一种电子设备和计算机可读存储介质，该方法包括：在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例（S101）；为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数（S102）；基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件（S103）。通过该方法，实现了HBASE的RegionServer在同一物理节点上部署多个实例，充分使用一个物理节点的资源，提高了HBASE集群稳定性。

Description

一种服务实例部署方法、装置、电子设备和存储介质
本申请要求于2020年7月28日提交中国专利局、申请号为202010738665.8、发明名称为“一种服务实例部署方法、装置及电子设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，更具体地说，涉及一种服务实例部署方法、装置、电子设备和计算机可读存储介质。
背景技术
HBASE(Hadoop Database，是一个高可靠性、高性能、面向列、可伸缩的分布式存储系统)的RegionServer(区域服务)提供具体的数据查询和插入，管理存储数据的region(区域)，对内存需求比较高。但是单个RegionServer不建议使用太高的内存，容易引发朱丽叶暂停，并且不利于稳定性。而Ambari管理平台默认只能一个节点安装一个RegionServer实例，在专门的HBASE物理集群下，无法充分有效地利用物理资源。
因此，如何在同一个物理节点上部署多个服务实例，充分使用一个物理节点的资源，提高HBASE集群稳定性是本领域技术人员需要解决的技术问题。
发明内容
本申请的目的在于提供一种服务实例部署方法、装置及一种电子设备和一种计算机可读存储介质，在同一个物理节点上部署多个服务实例，充分使用一个物理节点的资源，提高了HBASE集群稳定性。
为实现上述目的，本申请提供了一种服务实例部署方法，包括：
在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述 服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
其中，基于所述标志字符为每个所述服务实例分配对应的端口，包括：
基于所述标志字符在主函数参数位置添加每个所述服务实例对应的命令行，以便覆盖HBASE自身的端口配置，为每个所述服务实例分配对应的端口。
其中，还包括：
在JAVA虚拟机的设置位置添加每个所述服务实例对应的命令行，以便将每个所述服务实例标志字符作为对应的进程的系统参数。
其中，还包括：
基于所述标志字符在ambari的HBASE服务的元信息配置文件中添加每个所述服务实例对应的RegionServer组件；
基于所述标志字符在ambari的HBASE服务的角色操作顺序文件中添加每个所述服务实例对应的角色，并配置每个角色对应的操作的执行顺序；其中，所述服务实例对应的角色包括所述服务实例对应的RegionServer组件；
基于所述标志字符为每个所述服务实例创建对应的操作执行脚本，以便按照所述操作执行顺序执行对应的操作执行脚本。
其中，还包括：
基于所述标志字符在ambari的HBASE服务的警告配置文件中添加每个所述服务实例对应的告警模块，以便每个所述告警模块每隔第一预设时间检测所述服务实例对应的端口是否被使用，并对未被使用的端口对应的服务实例进行告警。
其中，还包括：
每个第二预设时间获取每个所述告警模块的告警内容，确定包含告警服务示例的告警节点，并统计所有所述告警节点的数量。
其中，还包括：
基于所述标志字符在ambari的监控组件中添加每个所述服务实例对应的监控指标，以便所述监控组件对每个所述服务实例的所有所述监控指标进行监控；
基于所述标志字符在ambari的HBASE服务的监控指标配置文件中添加每个所述服务实例对应的监控模块，以便每个所述监控模块从所述监控组件中获取对应的服务实例的所有所述监控指标；
基于所述标志字符在ambari的HBASE服务的窗口工具配置文件中添加每个所述服务实例对应的监控窗口，以便每个所述监控窗口显示对应的服务实例的所有所述监控指标。
为实现上述目的，本申请提供了一种服务实例部署装置，包括：
第一创建模块，用于在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
分配模块，用于为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
第二创建模块，用于基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
为实现上述目的，本申请提供了一种电子设备，包括：
存储器，用于存储计算机程序；
处理器，用于执行所述计算机程序时实现如上述服务实例部署方法的步骤。
为实现上述目的，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如上述服务实例部署方法的步骤。
通过以上方案可知，本申请提供的一种服务实例部署方法，包括：在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；基于所述标志字符为每个所 述服务实例创建对应的日志文件和pid文件。
本申请提供的服务实例部署方法，实现了HBASE的RegionServer在同一物理节点上部署多个实例，能够在相同region数的情况下减轻单个RegionServer的压力，也可以在同样总内存占用的情况下降低朱丽叶暂停的发生，提高了HBASE集群的稳定性，能够更充分地利用集群的物理资源，在没有物理扩容的情况下部署更多的RegionServer实例，在某些场景下降低扩容成本。本申请还公开了一种服务实例部署装置及一种电子设备和一种计算机可读存储介质，同样能实现上述技术效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本申请。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。附图是用来提供对本公开的进一步理解，并且构成说明书的一部分，与下面的具体实施方式一起用于解释本公开，但并不构成对本公开的限制。在附图中：
图1为根据一示例性实施例示出的一种服务实例部署方法的流程图；
图2为根据一示例性实施例示出的一种HBASE集群的结构图；
图3为根据一示例性实施例示出的一种服务实例部署装置的结构图；
图4为根据一示例性实施例示出的一种电子设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的 范围。
本申请实施例公开了一种服务实例部署方法，在同一个物理节点上部署多个服务实例，充分使用一个物理节点的资源，提高了HBASE集群稳定性。
参见图1，根据一示例性实施例示出的一种服务实例部署方法的流程图，如图1所示，包括：
S101：在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
本实施的执行主体为HBASE集群的管理节点，目的为在同一物理节点在部署多个服务实例。在本实施例中，在同一个目标物理节点中创建多个进程，每个进程为一个RegionServer组件，用于执行一个服务实例(即RegionServer实例)，即响应用户的读写请求，服务实例是HBASE的数据处理和计算单元，维护预写日志、读写缓存，管理多个Region。
S102：为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
在具体实施中，改造HBASE自身的执行方式，使其能识别操作RegionServer实例时执行命令中服务实例的标志字符，优选的，每个服务实例的标志字符可以在参数RegionServer上添加后缀的方式实现，基于该标志字符可以启动对应的RegionServer实例，并根据不同标志字符在启动JAVA进程时为不同服务实例添加上相应的系统参数和端口配置等。
具体的，基于所述标志字符为每个所述服务实例分配对应的端口的步骤包括：基于所述标志字符在主函数参数位置添加每个所述服务实例对应的命令行，以便覆盖HBASE自身的端口配置，为每个所述服务实例分配对应的端口。本实施例还包括：在JAVA虚拟机的设置位置添加每个所述服务实例对应的命令行，以便将每个所述服务实例标志字符作为对应的进程的系统参数。在具体实施中，在最终启动JAVA进程时，使用“-D参数名＝参数值”的方式添加三对到java命令行中(java[options]classname[args])，其中一对添加到“options”JVM(Java Virtual Machine，JAVA虚 拟机)设置的位置，以便将标志字符作为该进程的一个系统参数，另外两对添加到的“args”主函数参数的位置，以覆盖两个HBASE自身的端口相关配置，实现为不同标志字符的服务实例分配不同的两个端口。
S103：基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
在本步骤中，为不同服务实例创建对应的日志文件和pid(进程标识符，Process Identification)文件，Pid文件为文本文件，其内容仅有一行，记录了其对应进程的ID。基于其标志字符对文件进行命名，以供对应的进程进行使用，以实现在目标物理节点部署多个服务实例，如图2所示，HBASE集群包括两个物理节点，每个物理节点部署三个服务实例，每个服务实例的标识分别为RegionServer、RegionServer1和RegionServer2。管理节点中的Master(主机)与各物理节点中各服务实例分别连接。
作为一种优选实施方式，本实施例还包括：基于所述标志字符在ambari的HBASE服务的元信息配置文件中添加每个所述服务实例对应的RegionServer组件；基于所述标志字符在ambari的HBASE服务的角色操作顺序文件中添加每个所述服务实例对应的角色，并配置每个角色对应的操作的执行顺序；其中，所述服务实例对应的角色包括所述服务实例对应的RegionServer组件；基于所述标志字符为每个所述服务实例创建对应的操作执行脚本，以便按照所述操作执行顺序执行对应的操作执行脚本。
在具体实施中，改造ambari(一种基于Web的工具，支持Apache Hadoop集群的供应、管理和监控)的HBASE服务RegionServer组件的页面操作对应的后台执行步骤，使其能执行新添加的带有不同后缀的RegionServer组件的操作，如开始，停止，重启，开启安全模式和自动重启，并在整体操作HBASE服务时遵循正确的顺序。在ambari的HBASE服务的目录中的元信息配置文件中，新添的带有不同后缀的RegionServer组件，会去执行改造后的ambari操作RegionServer组件的步骤，改造后的步骤中，开启安全后需要执行的部分和其它RegionServer公有的部分如用户组权限检查等仍使用原本RegionServer的执行流程，最终调用HBASE本身的执行命令的部分如开始，停止，重启等，将在使用HBASE本身执行命令时在原 本的参数RegionServer上添加此处的后缀。在ambari的HBASE服务的目录中的角色操作顺序文件里，新添的带有不同后缀的HBASE-RegionServer角色，将会和HBASE-RegionServer同等级别依次执行。
本申请实施例提供的服务实例部署方法，实现了HBASE的RegionServer在同一物理节点上部署多个实例，能够在相同region数的情况下减轻单个RegionServer的压力，也可以在同样总内存占用的情况下降低朱丽叶暂停的发生，提高了HBASE集群的稳定性，能够更充分地利用集群的物理资源，在没有物理扩容的情况下部署更多的RegionServer实例，在某些场景下降低扩容成本。
在上述实施例的基础上，作为一种优选实施方式，还包括：基于所述标志字符在ambari的HBASE服务的警告配置文件中添加每个所述服务实例对应的告警模块，以便每个所述告警模块每隔第一预设时间检测所述服务实例对应的端口是否被使用，并对未被使用的端口对应的服务实例进行告警。
在具体实施中，在ambari的HBASE服务配置目录中的警告配置文件里新添的带有不同后缀的HBASE_RegionServer模块，即告警模块，将使ambari隔一段时间去检测带有该后缀组件所在节点对应的不同端口，并将在检测不到该端口被使用时在页面显示带有该后缀的HBASE_RegionServer红色警告信息，并显示出错内容。
优选的，本实施例还包括：每个第二预设时间获取每个所述告警模块的告警内容，确定包含告警服务示例的告警节点，并统计所有所述告警节点的数量。
在具体实施中，在server模块中，新添的带有后缀的子模块，将使ambari隔一段时间去检测上述模块的监控内容，并在上述模块报警时，统计带有该后缀组件总节点和报警节点的个数。
由此可见，本实施例可以在某些节点上新添加的带后缀的RegionServer组件宕掉后触发告警，并显示正常和异常的个数。
在上述实施例的基础上，作为一种优选实施方式，还包括：基于所述标志字符在ambari的监控组件中添加每个所述服务实例对应的监控指标，以便所述监控组件对每个所述服务实例的所有所述监控指标进行监控；基于所述标志字符在ambari的HBASE服务的监控指标配置文件中添加每个所述服务实例对应的监控模块，以便每个所述监控模块从所述监控组件中获取对应的服务实例的所有所述监控指标；基于所述标志字符在ambari的HBASE服务的窗口工具配置文件中添加每个所述服务实例对应的监控窗口，以便每个所述监控窗口显示对应的服务实例的所有所述监控指标。
在具体实施中，改造ambari的监控信息后台收集的流程，根据每个服务实例的标志字符将对应进程的监控指标名添加上不同的标记作为后缀形成新的指标名，区分不同进程的同一个监控内容，存储到ambari的监控组件后端存储中。在ambari的HBASE服务配置目录中的监控指标配置文件中，新添的不同后缀的HBASE_RegionServer模块，即监控模块，其下的监控指标名与上述的新指标名完全对应，使ambari能从监控组件后端存储取到不同后缀的RegionServer组件所在进程的监控指标内容。在ambari的HBASE服务配置目录中的窗口工具配置文件中，新添的不同后缀的监控窗口，在页面显示不同后缀的RegionServer组件的相应监控内容，如热点图HBASE Region数和监控读写次数，在其下子模块中，每个监控窗口所需运算的的监控指标名与所在添加后缀的上述指标名完全对应，使带有不同后缀名的监控窗口能够体现不同后缀名的RegionServer组件所在不同RegionServer进程的具体监控信息。和上述类似的，也能自定义窗口来显示不同后缀RegionServer组件的其它监控信息。
由此可见，本实施例可以展示新添加的带后缀的RegionServer的各种监控项，以及各种自定义组合监控。
下面介绍本申请提供的一种应用实施例，服务实例部署可以包括后台操作模块、页面操作模块、警告模块和监控模块，实现上述模块可以包括以下步骤：
步骤1：实现后台操作模块，改造HBASE自身的执行方式，使其能识 别在原本的操作RegionServer实例时执行的命令中参数“RegionServer”上添加的后缀，启动不同的RegionServer的实例。
步骤2：实现页面操作模块，改造Ambari的HBASE服务RegionServer组件的页面操作对应的后台执行步骤，使其能执行新添加的带有不同后缀的RegionServer组件的操作，如开始，停止，重启，开启安全模式和自动重启，并在整体操作HBASE服务时遵循正确的顺序。
步骤3：实现告警模块，在某些节点上新添加的带后缀的RegionServer组件宕掉后也能如原有RegionServer一样触发告警。并显示正常和异常的个数。
步骤4：实现监控模块，能够和原有RegionServer组件一样展示新添加的带后缀的RegionServer的各种监控项，以及各种自定义组合监控。
下面对本申请实施例提供的一种服务实例部署装置进行介绍，下文描述的一种服务实例部署装置与上文描述的一种服务实例部署方法可以相互参照。
参见图3，根据一示例性实施例示出的一种服务实例部署装置的结构图，如图3所示，包括：
第一创建模块301，用于在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
分配模块302，用于为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
第二创建模块303，用于基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
本申请实施例提供的服务实例部署装置，实现了HBASE的RegionServer在同一物理节点上部署多个实例，能够在相同region数的情况下减轻单个RegionServer的压力，也可以在同样总内存占用的情况下降低朱丽叶暂停的发生，提高了HBASE集群的稳定性，能够更充分地利用集群的物理资源，在没有物理扩容的情况下部署更多的RegionServer实例， 在某些场景下降低扩容成本。
在上述实施例的基础上，作为一种优选实施方式，所述分配模块302具体为为每个所述服务实例分配标志字符，基于所述标志字符在主函数参数位置添加每个所述服务实例对应的命令行，以便覆盖HBASE自身的端口配置，为每个所述服务实例分配对应的端口的模块。
在上述实施例的基础上，作为一种优选实施方式，还包括：
第一添加模块，用于在JAVA虚拟机的设置位置添加每个所述服务实例对应的命令行，以便将每个所述服务实例标志字符作为对应的进程的系统参数。
在上述实施例的基础上，作为一种优选实施方式，还包括：
第二添加模块，用于基于所述标志字符在ambari的HBASE服务的元信息配置文件中添加每个所述服务实例对应的RegionServer组件；
第三添加模块，用于基于所述标志字符在ambari的HBASE服务的角色操作顺序文件中添加每个所述服务实例对应的角色，并配置每个角色对应的操作的执行顺序；其中，所述服务实例对应的角色包括所述服务实例对应的RegionServer组件；
第三创建模块，用于基于所述标志字符为每个所述服务实例创建对应的操作执行脚本，以便按照所述操作执行顺序执行对应的操作执行脚本。
在上述实施例的基础上，作为一种优选实施方式，还包括：
第四添加模块，用于基于所述标志字符在ambari的监控组件中添加每个所述服务实例对应的监控指标，以便所述监控组件对每个所述服务实例的所有所述监控指标进行监控；
第五添加模块，用于基于所述标志字符在ambari的HBASE服务的监控指标配置文件中添加每个所述服务实例对应的监控模块，以便每个所述监控模块从所述监控组件中获取对应的服务实例的所有所述监控指标；
第六添加模块，用于基于所述标志字符在ambari的HBASE服务的窗口工具配置文件中添加每个所述服务实例对应的监控窗口，以便每个所述监控窗口显示对应的服务实例的所有所述监控指标。
在上述实施例的基础上，作为一种优选实施方式，还包括：
告警模块，用于基于所述标志字符在ambari的HBASE服务的警告配置文件中添加每个所述服务实例对应的告警模块，以便每个所述告警模块每隔第一预设时间检测所述服务实例对应的端口是否被使用，并对未被使用的端口对应的服务实例进行告警。
在上述实施例的基础上，作为一种优选实施方式，还包括：
统计模块，用于每个第二预设时间获取每个所述告警模块的告警内容，确定包含告警服务示例的告警节点，并统计所有所述告警节点的数量。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本申请还提供了一种电子设备，参见图4，本申请实施例提供的一种电子设备400的结构图，如图4所示，可以包括处理器11和存储器12。该电子设备400还可以包括多媒体组件13，输入/输出(I/O)接口14，以及通信组件15中的一者或多者。
其中，处理器11用于控制该电子设备400的整体操作，以完成上述的服务实例部署方法中的全部或部分步骤。存储器12用于存储各种类型的数据以支持在该电子设备400的操作，这些数据例如可以包括用于在该电子设备400上操作的任何应用程序或方法的指令，以及应用程序相关的数据。该存储器12可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，例如静态随机存取存储器(Static Random Access Memory，简称SRAM)，电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，简称EEPROM)，可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，简称EPROM)，可编程只读存储器(Programmable Read-Only Memory，简称PROM)，只读存储器(Read-Only Memory，简称ROM)，磁存储器，快闪存储器，磁盘或光盘。多媒体组件13可以包括屏幕，例如可以是触摸屏。I/O接口14为处理器11和其他接口模块之间提供接口，上述其他接口模块可以是键盘，鼠标，按钮等。这些按钮可以是虚拟按钮或者实体按钮。通信组件15用于该电子设备400 与其他设备之间进行有线或无线通信。无线通信，例如Wi-Fi，蓝牙，近场通信(Near Field Communication，简称NFC)，2G、3G或4G，或它们中的一种或几种的组合，因此相应的该通信组件15可以包括：Wi-Fi模块，蓝牙模块，NFC模块。
在一示例性实施例中，电子设备400可以被一个或多个应用专用集成电路(Application Specific Integrated Circuit，简称ASIC)、数字信号处理器(Digital Signal Processor，简称DSP)、数字信号处理设备(Digital Signal Processing Device，简称DSPD)、可编程逻辑器件(Programmable Logic Device，简称PLD)、现场可编程门阵列(Field Programmable Gate Array，简称FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述的服务实例部署方法。
在另一示例性实施例中，还提供了一种包括程序指令的计算机可读存储介质，该程序指令被处理器执行时实现上述服务实例部署方法的步骤。例如，该计算机可读存储介质可以为上述包括程序指令的存储器12，上述程序指令可由电子设备400的处理器11执行以完成上述的服务实例部署方法。
说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以对本申请进行若干改进和修饰，这些改进和修饰也落入本申请权利要求的保护范围内。
还需要说明的是，在本说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、 物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。

Claims (10)

  1. 一种服务实例部署方法，其特征在于，包括：
    在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
    为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
    基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
  2. 根据权利要求1所述服务实例部署方法，其特征在于，基于所述标志字符为每个所述服务实例分配对应的端口，包括：
    基于所述标志字符在主函数参数位置添加每个所述服务实例对应的命令行，以便覆盖HBASE自身的端口配置，为每个所述服务实例分配对应的端口。
  3. 根据权利要求1所述服务实例部署方法，其特征在于，还包括：
    在JAVA虚拟机的设置位置添加每个所述服务实例对应的命令行，以便将每个所述服务实例标志字符作为对应的进程的系统参数。
  4. 根据权利要求1所述服务实例部署方法，其特征在于，还包括：
    基于所述标志字符在ambari的HBASE服务的元信息配置文件中添加每个所述服务实例对应的RegionServer组件；
    基于所述标志字符在ambari的HBASE服务的角色操作顺序文件中添加每个所述服务实例对应的角色，并配置每个角色对应的操作的执行顺序；其中，所述服务实例对应的角色包括所述服务实例对应的RegionServer组件；
    基于所述标志字符为每个所述服务实例创建对应的操作执行脚本，以便按照所述操作执行顺序执行对应的操作执行脚本。
  5. 根据权利要求1所述服务实例部署方法，其特征在于，还包括：
    基于所述标志字符在ambari的HBASE服务的警告配置文件中添加每个所述服务实例对应的告警模块，以便每个所述告警模块每隔第一预设时间 检测所述服务实例对应的端口是否被使用，并对未被使用的端口对应的服务实例进行告警。
  6. 根据权利要求5所述服务实例部署方法，其特征在于，还包括：
    每个第二预设时间获取每个所述告警模块的告警内容，确定包含告警服务示例的告警节点，并统计所有所述告警节点的数量。
  7. 根据权利要求1所述服务实例部署方法，其特征在于，还包括：
    基于所述标志字符在ambari的监控组件中添加每个所述服务实例对应的监控指标，以便所述监控组件对每个所述服务实例的所有所述监控指标进行监控；
    基于所述标志字符在ambari的HBASE服务的监控指标配置文件中添加每个所述服务实例对应的监控模块，以便每个所述监控模块从所述监控组件中获取对应的服务实例的所有所述监控指标；
    基于所述标志字符在ambari的HBASE服务的窗口工具配置文件中添加每个所述服务实例对应的监控窗口，以便每个所述监控窗口显示对应的服务实例的所有所述监控指标。
  8. 一种服务实例部署装置，其特征在于，包括：
    第一创建模块，用于在目标物理节点中创建多个进程；其中，每个所述进程为一个RegionServer组件、用于执行一个服务实例；
    分配模块，用于为每个所述服务实例分配标志字符，并基于所述标志字符为每个所述服务实例分配对应的端口；其中，每个所述服务实例标志字符作为对应的进程的系统参数；
    第二创建模块，用于基于所述标志字符为每个所述服务实例创建对应的日志文件和pid文件。
  9. 一种电子设备，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于执行所述计算机程序时实现如权利要求1至7任一项所述服务实例部署方法的步骤。
  10. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1 至7任一项所述服务实例部署方法的步骤。
PCT/CN2021/076872 2020-07-28 2021-02-19 一种服务实例部署方法、装置、电子设备和存储介质 WO2022021850A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/005,945 US12020084B2 (en) 2020-07-28 2021-02-19 Service instance deployment method and apparatus, electronic device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010738665.8A CN111880810B (zh) 2020-07-28 2020-07-28 一种服务实例部署方法、装置及电子设备和存储介质
CN202010738665.8 2020-07-28

Publications (1)

Publication Number Publication Date
WO2022021850A1 true WO2022021850A1 (zh) 2022-02-03

Family

ID=73200892

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/076872 WO2022021850A1 (zh) 2020-07-28 2021-02-19 一种服务实例部署方法、装置、电子设备和存储介质

Country Status (3)

Country Link
US (1) US12020084B2 (zh)
CN (1) CN111880810B (zh)
WO (1) WO2022021850A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023070426A1 (zh) * 2021-10-28 2023-05-04 华为技术有限公司 一种配置方法和装置
WO2023201558A1 (zh) * 2022-04-20 2023-10-26 华为技术有限公司 一种映射关系生成方法、装置和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103259688A (zh) * 2013-06-04 2013-08-21 北京搜狐新媒体信息技术有限公司 一种分布式存储系统的故障诊断方法与装置
US20140188825A1 (en) * 2012-12-31 2014-07-03 Kannan Muthukkaruppan Placement policy
CN108549717A (zh) * 2018-04-23 2018-09-18 泰华智慧产业集团股份有限公司 自动化部署运维Hadoop生态圈组件的方法及系统
CN109257440A (zh) * 2018-10-29 2019-01-22 南京南瑞信息通信科技有限公司 一种基于服务注册中心的服务发现和客户端负载均衡方法
CN110825660A (zh) * 2019-09-27 2020-02-21 苏州浪潮智能科技有限公司 一种基于HBase的朱丽叶暂停优化方法、系统及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10642800B2 (en) * 2013-10-25 2020-05-05 Vmware, Inc. Multi-tenant distributed computing and database
US20160179494A1 (en) * 2014-12-18 2016-06-23 Vladimir Pavlov Integration of an arbitrary server installed as an extension of a computing platform
CN108563698B (zh) * 2018-03-22 2021-11-23 中国银联股份有限公司 一种HBase表的Region合并方法和装置
US10853368B2 (en) * 2018-04-02 2020-12-01 Cloudera, Inc. Distinct value estimation for query planning
CN109032674B (zh) * 2018-06-07 2021-08-24 烽火通信科技股份有限公司 一种多进程管理方法、系统及网络设备
US20200097847A1 (en) * 2018-09-21 2020-03-26 Gloudera, lnc. Hyperparameter tuning using visual analytics in a data science platform
US11301496B2 (en) * 2018-12-26 2022-04-12 Imperva, Inc. Using access logs for network entities type classification
CN110519100A (zh) * 2019-09-03 2019-11-29 浪潮云信息技术有限公司 一种多集群管理方法、终端及计算机可读存储介质
US11698820B2 (en) * 2020-02-25 2023-07-11 Hewlett Packard Enterprise Development Lp Autoscaling nodes of a stateful application based on role-based autoscaling policies

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140188825A1 (en) * 2012-12-31 2014-07-03 Kannan Muthukkaruppan Placement policy
CN103259688A (zh) * 2013-06-04 2013-08-21 北京搜狐新媒体信息技术有限公司 一种分布式存储系统的故障诊断方法与装置
CN108549717A (zh) * 2018-04-23 2018-09-18 泰华智慧产业集团股份有限公司 自动化部署运维Hadoop生态圈组件的方法及系统
CN109257440A (zh) * 2018-10-29 2019-01-22 南京南瑞信息通信科技有限公司 一种基于服务注册中心的服务发现和客户端负载均衡方法
CN110825660A (zh) * 2019-09-27 2020-02-21 苏州浪潮智能科技有限公司 一种基于HBase的朱丽叶暂停优化方法、系统及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
REN CHUN DUO DU SHU: "HBase Single-Node Deployment of Multiple RegionServers", CSDN BLOG, 5 March 2018 (2018-03-05), pages 1 - 4, XP009533653, Retrieved from the Internet <URL:https://blog.csdn.net/qq_35440040/article/details/79444064> [retrieved on 20220216] *

Also Published As

Publication number Publication date
US20230289238A1 (en) 2023-09-14
CN111880810B (zh) 2022-12-27
CN111880810A (zh) 2020-11-03
US12020084B2 (en) 2024-06-25

Similar Documents

Publication Publication Date Title
CN111314141B (zh) 路由更新方法及装置
US11513942B2 (en) Debug session management
US10379838B1 (en) Update and rollback of code and API versions
US10983896B2 (en) Debug event handling
US10268515B2 (en) Releasing resources from processes in a particular order to provide required resources to start an application
WO2017140131A1 (zh) 数据写入、读取方法及装置、云存储系统
US10785320B2 (en) Managing operation of instances
US9417870B2 (en) Managing user access to alternative versions of a particular function of a software product from within a current version of the software product
US10725763B1 (en) Update and rollback of configurations in a cloud-based architecture
US11550628B2 (en) Performing runbook operations for an application based on a runbook definition
CN103501237B (zh) 设备管理方法、管理平台、设备及系统
WO2022021850A1 (zh) 一种服务实例部署方法、装置、电子设备和存储介质
KR101368550B1 (ko) 모듈 보호 기능을 가진 단말기 및 이를 이용한 모듈 관리 방법
US8949930B1 (en) Template representation of security resources
US20190370137A1 (en) Testing framework for host computing devices
WO2021179487A1 (zh) 云主机在宿主机上的动态分配方法、电子装置及存储介质
US10185613B2 (en) Error determination from logs
CN115061841A (zh) 一种告警归并方法、装置、电子设备及存储介质
US11251976B2 (en) Data security processing method and terminal thereof, and server
US20220138023A1 (en) Managing alert messages for applications and access permissions
CN110879701B (zh) 工作流可视化配置方法、服务器、系统及介质
CN111399999A (zh) 计算机资源处理方法、装置、可读存储介质和计算机设备
CN114050990B (zh) 一种网络隔离设备的测试方法、装置、存储介质和电子设备
CN110798347B (zh) 服务状态检测方法、装置、设备及存储介质
US9178867B1 (en) Interacting with restricted environments

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21851471

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21851471

Country of ref document: EP

Kind code of ref document: A1