MarkLogic Performance Issue.

HI Guys,

I am Back again.

This is regarding the performance issue on MarkLogic

Below is the scenario where we found the issue.

we have two environments like testing and prod in the same cluster, we are running the Xquery script to get the some information it is taking 2X of time in prod compared to testing.

Below are the recommendations.


List Cache  size                     (1/8 of main memory )        
compressed tree cache size   (1/16 of main memory )
expanded tree cache size      (1/8 of main memory )


This is the short term solution.

Where in we have to move the testing environment to the other group or other  new cluster.

This is the long term solution.

Forest Migration at Local Node

Forest Migration is nothing but Change of Forest location one place to another place.


Now we can See 3 Forests Different Hosts .

Forest1->Primary Node
Forest2->Replica1 Node
Forest3->Replica2 Node




In our case all Forests are stored in data directory (/var/opt/MarkLogic)
But some Forest are created in different directory /var/MarkLoigc/data .

so we changed Forest directory like bellow /Var/opt/Mark Logic .

At we need create .Xml File. In XML file

1. Create migrate-forests.xml in node1 with below contents
<forest-migrate xmlns="http://marklogic.com/manage">
<forests>
<forest>Forest1</forest> /*forest name*/
</forests>
<host>mkl-dev-01.highroads.local</host> /*hostname*/
<data-directory>/var/opt/MarkLogic</data-directory> /*Directory_Name*/
<options>
<option>local-to-local</option>
</options>
</forest-migrate>


once created .xml file u need run this command to change old Forest location to new Forest location


2. Ran below curl command

curl --anyauth --user admin:admin -X PUT -d @"./migrate-forests.xml" -H 'Content-type: application/xml' 'http://mkl-dev-01.highroads.local:8002/manage/v2/forests'



Same procedure as to follow just replacing the forest name.Below are the two forests



now we can see Forest location changed to /var/opt/Marklogic/data to /var/opt/Marklogic.

MarkLogic upgarde

Hi Guys,

This post is to upgrade from 8.0-4.2 to 8.0-5.1 Marklogic database. This is the simple process here we used the single node for our testing upgardation.

Below are the steps.
1. Took the backup of all .xml files from /var/opt/Marklogic
2. re indexing is disabled (enable is false) on Database level for each database.
3.Stop the Marklogic service /etc/init.d/Marklogic stop
4.Uninstall the Marklogic here in RHEL we use as
    rpm -e Marklogic

5.Installed the rpm of 8.0-5.1 using the below command rpm -e 8.0-5.1 RPM

6. Login into the Admin Interface https://localhost:8001
7.You we will be redirecting to this page

8.Click ok to continue                                                                                                               

9.Now Marklogic will restart and open the Admin UI page as below as New                          Marklogic verison 8.0-5.1.                                         

10 Below is the previous verison 8.0-4.2 version of Marklogic.

MarkLogic Installation

Hi Guys,

Want to give overview on MarkLogic installation.

The prerequisties for Marklogic installation are below:-

Recommended RPM 's for Marklogic:-

yum install glibc.i686
yum install gdb
yum install redhat-lsb
yum install pstack
yum install sysstat

switch to the root user (if not)
sudo su -

Installation of MarkLogic:-

Move on to the /tmp folder

cd /tmp

Download the MarkLogic RPM from the MarkLogic website

http://developer.marklogic.com/products

Installing the rpm

rpm -i MarkLogic-8.0-1.x86_64.rpm (your rpm name)

start the Marklogic services

/etc/init.d/MarkLogic start

MarkLogic services status 

/etc/init.d/MarkLogic status