You can issue administrative queries to the MDEX Engine concurrently with running updates, without any interruptions caused by partial updates processing, except for the following administrative and configuration queries that are processed differently.

admin?op=exit and admin?op=restart queries cause the MDEX Engine to close its Dgraph port for accepting future queries. Next, the MDEX Engine processes all previously received queries and shuts down (or restarts, depending on which of these two commands is issued).

The admin?op=updateaspell operation causes the MDEX Engine to finish processing all existing preceding queries, temporarily stop processing other queries and begin to process admin?op=updateaspell. After it finishes processing this operation, the MDEX Engine resumes processing queries that queued up temporarily behind this request. Only one admin?op=updateaspell operation can be processed at a time.

config?op=update and admin?op=reload-services operations cause the MDEX Engine to drain all existing preceding queries, temporarily stop processing other queries and begin to process config?op=update and admin?op=reload-services. After it finishes processing these operations, the MDEX Engine resumes processing queries that queued up temporarily behind these requests.

Only one config?op=update operation can be processed at a time.

You can issue all other administrative queries to the MDEX Engine concurrently with updates, without any interruptions caused by partial updates processing.


Copyright © Legal Notices