Loading TOC...

XDMP-FORESTTAKEN

Message Text

Forest variable1 unexpectedly taken by host variable2

Cause

More than one host attempted to write to the same forest label. XDMP-FORESTTAKEN most often occurs when the host reporting the error loses connection with the rest of cluster, yet is still up. The failure sequence may be:

The problem host loses connection with the rest of the cluster and its networked storage. This might be due to excessive load or network connectivity problems.The cluster detects that the problem host is offline and fails its forests over to other hosts in the cluster.The problem host rejoins the cluster and discovers its forests have been taken by another host. The problem host then reports XDMP-FORESTTAKEN and restarts.

Response

If the host reporting XDMP-FORESTTAKEN is actually temporarily disconnected from its cluster, the system is performing as expected. No action is required.

If the cluster disconnection is unexpected, investigate the cause of the interruption. Possible causes include network interrupts, heavy load, or thread starvation on the reporting host.

If the cluster disconnection is due to regular, expected load, consider changing the host timeout or XDQP timeout. For more information, see Configuring Failover for a Forest in the Scalabilty, Availability, and Failover Guide. Increasing these timeouts increases how long it takes the system to detect and respond to a real outage.

Stack Overflow iconStack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.