MarkLogic Fundamentals FAQ - Common Error Messages
04 February 2022 05:05 PM


What does it mean?



This error may sometimes be encountered when:

  • When a restore is attempted while a backup task is running
  • Another process has the backup directory locked 

Seen when:

  • The disk containing the backup directory runs out of space
  • There's a bad disk configuration
  • The backup destination disk is unmounted


Indicates that an operation such as a merge, backup or query was explicitly canceled. This can occur:

  • Through the Admin Interface
  • By calling an explicit cancellation function, such as xdmp:request-cancel()
  • When a client breaks the network socket connection to the server while a query is running 


MarkLogic Server expects the system clocks to be synchronized across all the nodes in a cluster, as well as between Primary and Replica clusters. The acceptable level of clock skew (or drift) between hosts is less than 0.5 seconds, and values greater than 30 seconds will trigger XDMP-CLOCKSKEW errors, and could impact cluster availability


Indicates that an update statement attempted to perform an update to a document that will conflict with other updates occurring in the same statement. For example:

  • A single update transaction that attempts to updates a node, then attempts to add a child element to that node in the same transaction
  • A single update transaction that attempts to insert a document and then attempts to insert a node to that document
  • A single update transaction that attempts to insert a document at the same URI twice


Indicates that the same URI occurred in multiple forests of the same database. Under normal operating conditions, duplicate URIs are not allowed to occur, but there are ways that programmers and administrators can bypass the server safeguards


Indicates that MarkLogic Server detected a deadlock. Depending on whether the error is frequent or infrequent or whether it occurs as a ‘debug’ level or ‘notice’ level message, you need to take appropriate corrective action to avoid the deadlock


Indicates that MarkLogic has run out of room in the expanded tree cache during query evaluation, and that consequently it cannot continue evaluating the complete query


Indicates that a query or other operation exceeded its processing time limit. This can be caused by:

  • Inefficient queries
  • Inadequate processing limit
  • Resource bottlenecks


Indicates that in-memory storage is full, resulting in the forest stands being written out to disk. These are informational only and are not errors as MarkLogic Server is working as expected. However, if these messages consistently appear more frequently than once per minute, increasing the corresponding 'in-memory' settings in the affected database may be appropriate.

  • MarkLogic Server uses its list cache to hold search term lists in memory
  • If you're attempting to execute a particularly non-selective or inefficient query, your query will fail due to the size of the search term lists exceeding the allocated list cache


 Both errors indicate that the requested module does not exist or the user does not have the right permissions on the module

MarkLogic on AWS

What are 504 Timeout errors? How to resolve them?

504 timeout errors indicate that the load balancer may be closing the connection before the server responds to the request. To avoid these, make sure the idle time out setting is sufficient to receive responses from the MarkLogic server.


  • The error SVC-AWSCRED indicates that either no AWS security credentials are configured or there are issues recognizing IAM role
  • If you are using a non-managed instance using a custom AMI:
    • Add the below to your /etc/marklogic.conf file (create one if not present)
      • export MARKLOGIC_EC2_HOST=1
  • If you are using a managed AMI and want to use an IAM role:
    • Make sure you have below entries in mlcmd.conf which is available under /var/local/
(9 vote(s))
Not helpful

Comments (0)