I'm garnering comments / feedback concerning their experience around the
performance and stability of FTS for global search in ITSM 7.6.04 sp2
(ARS 7.6.04 sp3) in a server group environment with a large FTS index
collection.

 

I have an issue open with support currently where FTS plugin becomes
unresponsive because it keeps running out of Java heap space.

We have split the FTS indexer from the FTS searchers (per BMC support
recommendations in unpublished KA363429) , so all forward facing ars
servers (2 active) go against the same FTS process (we call it
FTS_searcher) on the primary admin sever.

So far BMC support has had us raise the Xmx from 1024 to 2048, and now
to 3072. FYI - this is x64 java process on Windows 2008 x64

 

Each time we have bump the Xmx it runs out for memory. I was able to
reproduce the rapid consumption of java memory by simply performing an
incident matching search, the FTS_searcher process used up 2Gb in less
than 10 seconds.

 

Additionally, I've seen the plugin still state it was out of java heap
even though the java process was no longer consuming the max Xmx defined
(I'm guessing because GC ran). Looks like a lack of recovery mechanisms
in place.

Our FTS collection folder is 34GB in size (is that large? Above the
average?), about 1.4 million incidents indexed will be the majority,
plus PBIs, CRQs, RKM KAs

 

If you have experienced similar behavior I'd love to hear your comments,
but I mainly want to try and gauge from the community (with a similar
setup) how stable they have seen this functionality to be.

 

We were almost ready to go live with 7.6.04, but this is a show stopper
- we can't have this instability. 

 

Regards,

 

Andrew C. Goodall

Software Engineer

Development Services

[email protected]

jcpenney

6501 Legacy Drive

Plano, TX 75024

jcp.com

 

<font face="monospace"size="-3"><br>The information transmitted is intended 
only for the person or entity to which it is addressed and <br>may contain 
confidential and/or privileged material. If the reader of this message is not 
the intended<br>recipient, you are hereby notified that your access is 
unauthorized, and any review, dissemination,<br>distribution or copying of this 
message including any attachments is strictly prohibited. If you are not<br>the 
intended recipient, please contact the sender and delete the material from any 
computer.<br>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to