Re: Processing backlog in "schedule" table for the "linker" processes (566 Views)
Reply
Occasional Contributor
Posts: 3
Registered: ‎10-31-2011
Message 1 of 5 (590 Views)

Processing backlog in "schedule" table for the "linker" processes

Hi,

 

The schedule table of our SM9.21 implementation gets a lot of records under the linker class for setting the interaction status to Open-Linked.

 

Because of this high load, the linker process starts to lag out and we get a backlog of a few hours worth of unprocessed schedule records.

 

Our is a horizontally scaled environment and we have a load balancer and two other nodes running. The linker is currently only running on the LB.

 

Will it help if we start more linker processes - one each on the other two nodes? Or will it cause more trouble?

 

Is there any other way to speed up the rate at which linker is crunching these records?

 

Regards,

KM

Honored Contributor
Posts: 900
Registered: ‎10-14-2010
Message 2 of 5 (583 Views)

Re: Processing backlog in "schedule" table for the "linker" processes

hi you can start linker for both App server it wont harm but occupy some memory...

Occasional Contributor
Posts: 3
Registered: ‎10-31-2011
Message 3 of 5 (579 Views)

Re: Processing backlog in "schedule" table for the "linker" processes

Thanks Abhijit,

Is there any other way for us to speed up the linker processing?

 

-Karan

Honored Contributor
Posts: 1,382
Registered: ‎04-19-2011
Message 4 of 5 (567 Views)

Re: Processing backlog in "schedule" table for the "linker" processes

In Horizontal based environment, I hope all SM background process would be running on load balancer port, not on other ports.

 

Anyhow you can add up new linker process and check whether that would speed up the process.

 

First of all, I would suggest you to find why linker process is taking lot of time to process records.

Highlighted
Advisor
Posts: 14
Registered: ‎04-30-2010
Message 5 of 5 (566 Views)

Re: Processing backlog in "schedule" table for the "linker" processes

Good starting point could be the tracing the linker process.

 

The following command is for the linker background process:

sm -bg scheduler linker 60 1 -RTM:3 -debugdbquery:999 -log:linker.log

 

Before applying, please have a look at:

 

http://support.openview.hp.com/selfsolve/document/KM480574

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.