CN108959501B - Method and device for deleting ES index - Google Patents
Method and device for deleting ES index Download PDFInfo
- Publication number
- CN108959501B CN108959501B CN201810671753.3A CN201810671753A CN108959501B CN 108959501 B CN108959501 B CN 108959501B CN 201810671753 A CN201810671753 A CN 201810671753A CN 108959501 B CN108959501 B CN 108959501B
- Authority
- CN
- China
- Prior art keywords
- index
- server
- request
- deleting
- sending
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
Abstract
In order to solve the problems in the related art, the present disclosure provides a method and an apparatus for deleting an ES index. The method comprises the following steps: generating an ES index deleting command, wherein the ES index deleting command indicates an ES index to be deleted in a target data source; placing index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, wherein the ES indexes to be deleted in one set are generated according to the same period; for any set, sending a request for deleting a first ES index in the set to the ES server so that the ES server deletes the first ES index from the target data source; and when determining that the first ES index does not exist in the target data source, sending a request for deleting the next ES index in the set to the ES server until all the ES indexes in the set are deleted. The method and the device reduce the complexity of ES index deletion and reduce labor cost.
Description
Technical Field
The present disclosure relates to the field of database technologies, and in particular, to a method and an apparatus for deleting an ES index.
Background
At present, big data bring great changes to people's life, and applications such as mobile payment, voice recognition, facial recognition, system images, shared objects, artificial intelligence and the like which are emerging at present need to be realized by means of big data technology. One piece of data has a life cycle (life cycle) corresponding to the data, and the generation, use, migration, cleaning and destruction of the data integrate data experience, data cleaning, historical information inquiry and knowledge sharing. For one system, in order to ensure stable and efficient operation of the system, it is necessary to control the Data amount to a stable level, and based on this, DLM (Data Life Cycle Management) is born. If the data is divided according to time, the data can be divided into: hot data, warm data, cold data, data at the freezing and thawing stages. The cold data generally needs to be backed up, archived, deleted, etc. In one scenario, the amount of data generated by an enterprise providing data monitoring services every day is huge, and if the set storage days are seven days and the data before seven days are cold data, the source data lose significance and occupy a large storage space, in which case, a deletion operation needs to be performed on the cold data.
ES, the elastic search, provides a distributed multi-user capable full-text search engine. The index (index) of the ES is a logical storage of logical data by the ES, and the structure of the index is prepared for fast and efficient full-text indexing, which does not store the original value, and the retrieval data thereof is output in json form.
Disclosure of Invention
In order to solve the problem that the operation of deleting the ES index is complex in the related art, the disclosure provides a method and a device for deleting the ES index.
According to one aspect of the present disclosure, there is provided a method for deleting an ES index, the method being applied to a client, and including: generating an ES index deleting command, wherein the ES index deleting command indicates an ES index to be deleted in a target data source; placing index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, wherein the ES indexes to be deleted in one set are generated according to the same period; for any set, sending a request for deleting a first ES index in the set to an ES server so that the ES server deletes the first ES index from the target data source; and when determining that the first ES index does not exist in the target data source, sending a request for deleting the next ES index in the set to the ES server until all the ES indexes in the set are deleted.
According to a second aspect of the present disclosure, there is provided an apparatus for deleting an ES index, the apparatus being applied to a client, and including: the generating module is used for generating an ES index deleting command, and the ES index deleting command indicates an ES index to be deleted in the target data source; the device comprises a setting module, a deletion module and a deletion module, wherein the setting module is used for placing index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, and the ES indexes to be deleted in one set are generated according to the same period; a first sending module, configured to send, to an ES server, a request to delete a first ES index in an ES set for any set, so that the ES server deletes the first ES index from the target data source; and a second sending module, configured to send, to the ES server, a request to delete a next ES index in the set until all ES indexes in the set are deleted, when it is determined that the first ES index does not exist in the target data source.
According to the method for deleting the ES index, the index generated in the latest period of time can be reserved regularly according to the ES index deleting command, the indexes generated at other times except the period of time are deleted, the index deleting script does not need to be edited additionally according to the field condition of the system, the complexity of ES index deletion is reduced, and the labor cost is reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow diagram illustrating a method of deleting an ES index in accordance with an exemplary embodiment;
FIG. 2 is a schematic diagram illustrating a naturally occurring index in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram illustrating a monthly generated index in accordance with an exemplary embodiment;
FIG. 4 is a schematic diagram illustrating an annual generated index in accordance with an exemplary embodiment;
FIG. 5 is a flow diagram illustrating a method of deleting an ES index in accordance with an exemplary embodiment;
fig. 6 is a block diagram illustrating an apparatus for deleting an ES index according to an exemplary embodiment.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
The ES index timing deletion mechanism plays a critical role in disk warning and storage planning. The timed deletion operation of the ES index may be to delete the ES index at a timed manner according to the generation manner of the ES index, for example, for the ES index generated by day, the ES index is deleted by day. However, under the condition of large field data pressure of the system, an index deletion script is generally written according to the field condition of the system, and after relevant parameters are configured, the index deletion script is run at regular time by using the crontab, but the complexity of a regular deletion index mechanism and the labor cost are increased by additionally adding the index deletion script.
Fig. 1 is a flowchart illustrating a method for deleting an ES index according to an exemplary embodiment, which may be implemented by a client, for example, by configuring an ES index deletion command on the client, sending a request to a server according to the ES index deletion command, requesting to delete the corresponding ES index, and the client may confirm whether the ES index is successfully deleted by interacting with the ES server. The client and the ES server may be deployed on the same device, or may be deployed separately, as long as they can communicate with each other, and the disclosure is not limited thereto. As shown in fig. 1, the method includes:
step 101: generating an ES index deleting command, wherein the ES index deleting command indicates an ES index to be deleted in a target data source;
in the present disclosure, the ES indexes in the target data source may include ES indexes generated in various periods, such as daily generation, monthly generation, daily generation, and the like, and may also include ES indexes generated non-periodically.
In one implementation manner, the ES index deletion command may be generated according to a user trigger, for example, if the user instructs to delete the ES index to be deleted on the client, the ES index deletion command is generated; the ES index deleting command may also be generated periodically, for example, a timer may be configured in advance, and when the timer expires, the ES index deleting command is generated, and then the timer is reset to start to count again.
The ES index deletion command may be used to instruct retention of the ES index generated within the latest period of time, i.e., deletion of the ES index generated at a time other than the latest period of time. When the generated ES index deleting command is triggered by the user, the time length of the latest period of time can be specified by the user; when the ES index deleting command is generated periodically, the time length of the latest period of time may be less than the time length of the timer, or may be greater than or equal to the time length of the timer, which is not limited in this disclosure. For example, an ES index deletion command is generated every 7 days, and the ES index deletion command may indicate that an ES index generated within the last 5 days is to be retained, may indicate that an ES index generated within the last 10 days is to be retained, and may indicate that an ES index generated within the last 7 days is to be retained.
Step 102: and placing the index name of the ES index to be deleted in the target data source indicated in the ES index deletion command into a set, wherein the ES index to be deleted in one set is generated according to the same period.
The ES indexes to be deleted indicated in the ES index deletion command may include ES indexes generated in a plurality of periods, or may include non-periodically generated ES indexes, where the ES indexes generated in the same period may be put into one set. The ES indexes to be deleted in the set can be sorted according to the generated time.
Step 103: for any set, sending a request for deleting a first ES index in the set to an ES server; wherein, the set comprises index names of ES indexes to be deleted in the target data source;
step 104: and when determining that the first ES index does not exist in the target data source, sending a request for deleting the next ES index in the set to the ES server until all the ES indexes in the set are deleted.
According to the method for deleting the ES index, the index generated in the latest period of time can be reserved according to the ES index deleting command, the indexes generated at other times except the period of time are deleted, the index deleting script does not need to be additionally edited according to the field condition of the system, the complexity of ES index deletion is reduced, and the labor cost is reduced.
To facilitate the description of the method for deleting the ES index in the present disclosure, first, a description is given of a generation method of the index in the present disclosure with reference to fig. 2.
Data can generally enter an ES (electronic storage system) through logstack parsing and java programs, the data can be matched with an ES index template before entering the ES, when the data is matched with the ES index template, the data which accords with a certain ES index template enters the index template, and an ES index can be created by using a predefined template. For example, the name of an index template is template _1, the template defines that template is "te ×", which means that the template is valid for all new indexes at the beginning of te, the template includes two attributes of settings and maps, which can configure the generation mode of the index, such as the index generated by day, month or year, wherein the index generated by day is shown in fig. 2, the index names are snmp-data-2017.12.10 and snmp-data-2017.12.11 …, wherein 2017.12.10 and 2017.12.11 indicate the date of the index generation; the indexes generated by month are shown in FIG. 3, and the index names are zjj-2017.01, zjj-2017.02 …, wherein 2017.01 and 2017.02 represent the generation months of the indexes; the index generated by year is shown in FIG. 4, and the index names flow _ ndp-2015, flow _ ndp-2016, 2015, 2016 indicate the generation year of the index.
Based on the generation manner of the index, in an implementation manner, the method for deleting the ES index of the present disclosure may further include: after the generating the ES index deletion command, the method further includes: when determining that the ES index to be deleted is not the ES index generated according to any preset period, sending a request for deleting the index data of the ES index to be deleted to an ES server, so that the ES server deletes the index data of the ES index to be deleted from the target data source. Since the deletion of the index data causes a problem such as memory leak, the deletion of the index data is performed only when the data amount is small. When the ES index to be deleted is an ES index which is generated non-periodically, the data volume of the ES index is considered to be less, and a request for deleting the index data of the ES index to be deleted is sent to an ES server. For example, if the ES index name suffix shows that the ES index is according to a fixed period, for example, the ES index suffix is in the form of "-year, month, day", which indicates that the ES index is generated by the day, the ES index is deleted later; if the ES index is not generated according to the fixed period, the ES index can be considered to store a small number of documents (namely, less data), and the subsequent deletion of the data of the ES index can achieve the purpose of cleaning the data of the index which is generated in a small amount and non-periodically, so that the disk space is saved.
In the following, the deletion index and the deletion index data are respectively exemplified, when deleting the index, for example, there is an index with an index name of zjj-2017.01.01, and there are 1000 documents inside, and after executing the deletion index, the index disappears, that is, is deleted; also named zjj-2017.01.01, which contains 1000 documents, which still exist after the delete index data operation is performed, but the number of documents becomes 0.
In one implementation manner, determining whether the ES index to be deleted is an ES index generated in a fixed period may include: and judging whether the ES index to be deleted is the ES index generated according to the fixed period or not according to the index name of the ES index to be deleted. Whether the suffix of the ES index to be deleted contains the time period identifier may be determined, and when the suffix of the ES index contains the time period identifier, it is determined that the ES index is generated according to the fixed period, and when the suffix of the ES index does not contain the time period identifier, it is determined that the ES index is not generated according to the fixed period. For example, an index suffix generated by day is in the form of "-year.month.day", an index suffix generated by month is in the form of "-year.month", and an index suffix generated by year is in the form of "-year", wherein each year, month, and day can be identified as an identification of a time period. Based on the judgment of the generation mode of the ES index, the ES index can be distinguished when the data of the ES index is deleted subsequently, only a small amount of data of the ES index which is not generated according to a fixed period is ensured to be deleted, and the problems of memory leakage and the like caused by deleting the data of the ES index are avoided.
In one implementation, determining that the first ES index does not exist in the target data source includes: after sending a request for deleting a first ES index in the set to an ES server, waiting for a preset time length, and sending a first confirmation request to the ES server; when determining that the deletion of the first ES index fails according to first information returned by the ES server aiming at the first confirmation request, sending a second confirmation request to the ES server; and when determining that the deletion of the first ES index is successful according to the first information returned by the ES server aiming at the first confirmation request, executing the step of sending a request for deleting the next ES index in the set to the ES server. Sending a first confirmation request to the ES server to request confirmation of whether the ES index is successfully deleted may be implemented by calling prepareddelete () in an API (Application Programming Interface) of the ES, and determining whether the ES index is successfully deleted according to a value of isacknowledded () returned by the ES server, where the value of isacknowledded () returned by the server is used as an example of the first information, and when the value is true, it indicates that the ES index is successfully deleted, and when the value is false, it indicates that the ES index is unsuccessfully deleted; sending a second confirmation request to the ES server to request confirmation of whether the deleted ES index exists in the target data source may be implemented by calling isExists () in the API interface of the ES, determining that the ES index still exists in the target data source when the ES server returns the value as true, and determining that the ES index does not exist in the target data source when the ES server returns the value as false. After the first ES index is requested to be deleted from the ES server, whether the ES index is successfully deleted is requested to be confirmed from the ES server, and if the ES index is successfully deleted, whether the ES index still exists in the target data source is continuously requested to be confirmed from the ES server, so that the ES index can be further successfully deleted, the deletion operation of the previously unsuccessfully deleted index is not required to be executed again in the next processing period, and the disk load is reduced.
In one implementation, the method for deleting the ES index may further include: after sending the second confirmation request to the ES server, if it is determined that the first ES index exists in the target data source according to the second information returned by the ES server for the second confirmation request, for example, in a case where after invoking isExists () in the API interface of the ES, the ES server returns that the value (which may be an example of the second confirmation information) of the isExists is true, sending a request to delete the first ES index to the ES server, and executing a step of sending a request to delete the next ES index in the set to the ES server until the number of times of sending the request to delete the first ES index to the ES server reaches a threshold value, for example, three times; and when it is determined that the first ES index does not exist in the target data source according to second information returned by the ES server for the second confirmation request, for example, when the ES server returns false after invoking isExists () in the API interface of the ES, a step of sending a request for deleting a next ES index in the set to the ES server is performed.
Fig. 5 is a flowchart illustrating a method of deleting ES indexes according to an exemplary embodiment, where the deletion of ES indexes generated by day is taken as an example, for convenience of description, the ES indexes are simply referred to as indexes, and an ES server is simply referred to as a server, as shown in fig. 5, and the method includes the following processes:
step 501: generating an ES index deletion command;
wherein the operation of deleting the index indicates to delete the ES index in the target data source;
for example, assuming that the current time is 2018, 5/9/day, the generated ES index deletion command indicates to delete an index generated before 2018, 5/3/day, and to reserve indexes generated during a period from 2018, 5/3/day to 2018, 5/9/day (including indexes generated during 2018, 5/3/day, and 2018, 5/9/day), that is, indexes generated during the last 7 days.
Step 502: putting the index name of the ES index to be deleted into a set list;
for example, the index names of the indexes to be deleted are zjj-2017.01.01, zjj-2017.01.02 and zjj-2017.01.03 respectively, and the indexes are generated by days, so that the elements in list 1 are zjj-2017.01.01, zjj-2017.01.02 and zjj-2017.01.03 respectively;
for another example, the index names of the indexes to be deleted are zjj-2017.01, zjj-2017.02 and zjj-2017.03 respectively, and the indexes are generated monthly, so that the elements in list 2 are zjj-2017.01, zjj-2017.02 and zjj-2017.03 respectively.
Step 503: for each set list, sending a request for deleting a first ES index in the list to the ES server, where the request may include an index name of the first index, for example, for list 1, the sent request includes index names zjj-2017.01.01 of the first index; for list 2, the request sent contains the index name zjj-2017.01 of the first index;
step 504: sleeping the thread for one minute;
step 505: calling prepareddelete () in an API of the ES, when the value of isacknowleded () returned by the ES server is true, representing that the first index deletion is successful, executing step 506, when the value of isacknowleded () returned by the ES server is false, representing that the first index deletion is failed, executing step 507;
step 506: sending a request for deleting the next index in the list to the ES server, wherein the next index is an index with the index name of zjj-2017.01.02 in the list 1; or indexes with the index names of zjj-2017.02 in list 2;
step 507: and invoking isExists () in an API (application programming interface) of the ES, judging whether the first ES index exists in the target data source, determining that the first ES index exists in the target data source when the ES server returns true, executing step 508, determining that the first ES index does not exist in the target data source when the ES server returns false, and returning to execute step 506.
Step 508: and re-sending the request for deleting the first index to the ES server, and returning to perform step 506 until the number of times of sending the request for deleting the first index to the ES server reaches a threshold, where the threshold may be 3.
Fig. 6 is a block diagram illustrating an apparatus for deleting an ES index according to an exemplary embodiment, and as shown in fig. 6, the apparatus 60 includes the following components:
a generating module 61, configured to generate an ES index deletion command, where the ES index deletion command indicates an ES index to be deleted in a target data source;
the setting module 62 is configured to put index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, where the ES indexes to be deleted in one set are generated according to the same period.
In one implementation, the ES delete command is generated periodically for a preset period of time.
A first sending module 63, configured to send, to an ES server, a request to delete a first ES index in an ES set, so that the ES server deletes the first ES index from the target data source;
a second sending module 64, configured to send, to the ES server, a request to delete a next ES index in the set until all ES indexes in the set are deleted, when it is determined that the first ES index does not exist in the target data source.
In an implementation manner, the apparatus for deleting the ES index may further include: and a third sending module, configured to send, when it is determined that the ES index to be deleted is not an ES index generated according to any preset period, a request for deleting the index data of the ES index to be deleted to the ES server, so that the ES server deletes the index data of the ES index to be deleted from the target data source.
In one implementation, the second sending module includes: a first sending unit, configured to wait for a preset duration after sending a request for deleting a first ES index in the set to an ES server, and send a first confirmation request to the ES server; a second sending unit, configured to send a second acknowledgement request to the ES server when determining that deletion of the first ES index fails according to first information returned by the ES server for the first acknowledgement request; and the execution unit is used for executing the step of sending a request for deleting the next ES index in the set to the ES server when the first ES index is determined to be successfully deleted according to the first information returned by the ES server aiming at the first confirmation request.
In an implementation manner, the apparatus for deleting the ES index may further include: a second execution module, configured to send, when it is determined that the first ES index exists in the target data source according to second information returned by the ES server for the second confirmation request, a request to delete the first ES index to the ES server, and execute a step of sending, to the ES server, a request to delete a next ES index in the set until a number of times of sending, to the ES server, the request to delete the first ES index reaches a threshold; a third executing module, configured to execute the step of sending a request to delete a next ES index in the set to the ES server when it is determined that the first ES index does not exist in the target data source according to the second information returned by the ES server for the second confirmation request.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (6)
1. A method for deleting an ES index is applied to a client and comprises the following steps:
generating an ES index deleting command, wherein the ES index deleting command indicates an ES index to be deleted in a target data source; the ES index deleting command is generated periodically, a timer is configured in advance, and when the timer is up, the ES index deleting command is generated; placing index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, wherein the ES indexes to be deleted in one set are generated according to the same period;
for any set, sending a request for deleting a first ES index in the set to an ES server so that the ES server deletes the first ES index from the target data source;
when determining that the first ES index does not exist in the target data source, sending a request for deleting the next ES index in the set to the ES server until all ES indexes in the set are deleted;
after generating the ES index delete command, the method further comprises:
when determining that the ES index to be deleted is not the ES index generated according to any preset period, sending a request for deleting the index data of the ES index to be deleted to an ES server, so that the ES server deletes the index data of the ES index to be deleted from the target data source.
2. The method of claim 1, wherein determining that the first ES index is not present in the target data source comprises:
after sending a request for deleting a first ES index in the set to an ES server, waiting for a preset time length, and sending a first confirmation request to the ES server;
when determining that the deletion of the first ES index fails according to first information returned by the ES server aiming at the first confirmation request, sending a second confirmation request to the ES server;
and when determining that the deletion of the first ES index is successful according to the first information returned by the ES server aiming at the first confirmation request, executing the step of sending a request for deleting the next ES index in the set to the ES server.
3. The method of claim 2, further comprising:
when determining that the first ES index exists in the target data source according to second information returned by the ES server according to the second confirmation request, sending a request for deleting the first ES index to the ES server, and executing a step of sending a request for deleting a next ES index in the set to the ES server until the number of times of sending the request for deleting the first ES index to the ES server reaches a threshold value;
and when determining that the first ES index does not exist in the target data source according to the second information returned by the ES server for the second confirmation request, executing a step of sending a request for deleting a next ES index in the set to the ES server.
4. An apparatus for deleting an ES index, the apparatus being applied to a client and comprising:
the generating module is used for generating an ES index deleting command, and the ES index deleting command indicates an ES index to be deleted in the target data source; the ES index deleting command is generated periodically, a timer is configured in advance, and when the timer is up, the ES index deleting command is generated;
the device comprises a setting module, a deletion module and a deletion module, wherein the setting module is used for placing index names of the ES indexes to be deleted in the target data source indicated in the ES index deletion command into sets, and the ES indexes to be deleted in one set are generated according to the same period;
a first sending module, configured to send, to an ES server, a request to delete a first ES index in an ES set for any set, so that the ES server deletes the first ES index from the target data source;
a second sending module, configured to send, to the ES server, a request to delete a next ES index in the set until all ES indexes in the set are deleted, when it is determined that the first ES index does not exist in the target data source;
the device further comprises:
and a third sending module, configured to send, after generating the ES index deletion command, a request to delete the index data of the ES index to be deleted to the ES server when it is determined that the ES index to be deleted is not an ES index generated according to any preset period, so that the ES server deletes the index data of the ES index to be deleted from the target data source.
5. The apparatus of claim 4, wherein the second sending module comprises:
a first sending unit, configured to wait for a preset duration after sending a request for deleting a first ES index in the set to an ES server, and send a first confirmation request to the ES server;
a second sending unit, configured to send a second acknowledgement request to the ES server when determining that deletion of the first ES index fails according to first information returned by the ES server for the first acknowledgement request;
and the execution unit is used for executing the step of sending a request for deleting the next ES index in the set to the ES server when the first ES index is determined to be successfully deleted according to the first information returned by the ES server aiming at the first confirmation request.
6. The apparatus of claim 5, further comprising:
a second execution module, configured to send, when it is determined that the first ES index exists in the target data source according to second information returned by the ES server for the second confirmation request, a request to delete the first ES index to the ES server, and execute a step of sending, to the ES server, a request to delete a next ES index in the set until a number of times of sending, to the ES server, the request to delete the first ES index reaches a threshold;
a third executing module, configured to execute the step of sending a request to delete a next ES index in the set to the ES server when it is determined that the first ES index does not exist in the target data source according to the second information returned by the ES server for the second confirmation request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810671753.3A CN108959501B (en) | 2018-06-26 | 2018-06-26 | Method and device for deleting ES index |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810671753.3A CN108959501B (en) | 2018-06-26 | 2018-06-26 | Method and device for deleting ES index |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108959501A CN108959501A (en) | 2018-12-07 |
| CN108959501B true CN108959501B (en) | 2021-09-17 |
Family
ID=64486858
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810671753.3A Active CN108959501B (en) | 2018-06-26 | 2018-06-26 | Method and device for deleting ES index |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108959501B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111461537A (en) * | 2020-03-31 | 2020-07-28 | 山东胜软科技股份有限公司 | Oil gas production data based classified quantity counting method and control system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9646172B1 (en) * | 2016-11-15 | 2017-05-09 | Envieta Systems LLC | Data storage system for securely storing data records |
| CN106649870A (en) * | 2017-01-03 | 2017-05-10 | 山东浪潮商用系统有限公司 | Distributed implementation method for search engine |
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN107016025A (en) * | 2016-11-17 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of method for building up and device of non-relational database index |
| CN107153535A (en) * | 2017-03-27 | 2017-09-12 | 武汉斗鱼网络科技有限公司 | A kind of operation ElasticSearch method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10331649B2 (en) * | 2014-06-29 | 2019-06-25 | Microsoft Technology Licensing, Llc | Transactional access to records on secondary storage in an in-memory database |
| JP2016197836A (en) * | 2015-04-06 | 2016-11-24 | 富士通株式会社 | Packet transmission device |
| CN106528557A (en) * | 2015-09-10 | 2017-03-22 | 北京国双科技有限公司 | Method and device for detecting data rows deleted from data table |
| CN105426128A (en) * | 2015-11-16 | 2016-03-23 | 浪潮集团有限公司 | Index maintenance method and device |
| CN106649461A (en) * | 2016-09-26 | 2017-05-10 | 浪潮电子信息产业股份有限公司 | Method for automatically cleaning and maintaining elastic search log index file |
-
2018
- 2018-06-26 CN CN201810671753.3A patent/CN108959501B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| US9646172B1 (en) * | 2016-11-15 | 2017-05-09 | Envieta Systems LLC | Data storage system for securely storing data records |
| CN107016025A (en) * | 2016-11-17 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of method for building up and device of non-relational database index |
| CN106649870A (en) * | 2017-01-03 | 2017-05-10 | 山东浪潮商用系统有限公司 | Distributed implementation method for search engine |
| CN107153535A (en) * | 2017-03-27 | 2017-09-12 | 武汉斗鱼网络科技有限公司 | A kind of operation ElasticSearch method and device |
Non-Patent Citations (2)
| Title |
|---|
| Space Reduction for Contextual Transaction Trust Computation in E-Commerce and E-Service Environments;H. Zhang等;《015 IEEE International Conference on Services Computing》;20150702;680-687 * |
| 基于HBase+ ElasticSearch的海量交通数据实时存取方案设计;董长青 等;《大数据》;20170120;第3卷(第1期);80-89 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108959501A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109857737B (en) | Cold and hot data storage method and device and electronic equipment | |
| US10956374B2 (en) | Data recovery method, apparatus, and system | |
| CN110175677A (en) | Automatic update method, device, computer equipment and storage medium | |
| CN109144785B (en) | Method and apparatus for backing up data | |
| WO2019237797A1 (en) | Data backup method and apparatus | |
| CN105279261A (en) | Dynamic extensible database filing method and system | |
| CN111767144B (en) | Transaction route determination method, device, equipment and system for transaction data | |
| CN110602165B (en) | Government affair data synchronization method, device, system, computer equipment and storage medium | |
| CN109697112B (en) | Distributed intensive one-stop operating system and implementation method | |
| CN112632375B (en) | Session information processing method, server and storage medium | |
| CN113760513A (en) | Distributed task scheduling method, device, equipment and medium | |
| CN111240892A (en) | Data backup method and device | |
| CN111367948B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN113282580A (en) | Method, storage medium and server for executing timed task | |
| CN106874343B (en) | Data deletion method and system for time sequence database | |
| CN108959501B (en) | Method and device for deleting ES index | |
| CN116701063B (en) | Persistence method, device and system for internal memory state data for data language of digital networking | |
| CN115878386A (en) | Disaster recovery method and device, electronic equipment and storage medium | |
| CN106383664B (en) | Date storage method and device | |
| US11580128B2 (en) | Preventing DBMS deadlock by eliminating shared locking | |
| CN114254278A (en) | User account merging method and device, computer equipment and storage medium | |
| CN105242951A (en) | UUID calling method for software application | |
| Mand et al. | Authentication tokens based smart backup and recovery system for modern android systems | |
| CN111259023B (en) | Data scheduling method and device, electronic equipment and storage medium | |
| CN116303240B (en) | Snapshot establishment method, system, equipment and medium of distributed file system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |