Re: Recommended size for FTS index collection directory
Not an FTS fan at this point. I have a huge knot in my head from FTS troubles - but that is a story for another day. In a server group only one server needs access to the collection folder the others point to a searcher plugin on the primary fts server that reads the collection. We have 43GB FTS collection. INC = 1.3million PBI = 5600 CHG = 13500 WOI = 9600 REQ = 82400 KA = 15500 The size just doesn't depend on the number of records though - it also depends on the number of fields you have added for FTS / MFS indexing and how you have config'd the Title, Environment, Keywords (in form properties). Also note the larger the collection size the larger the memory max (Xmx) for your jvm fts searcher process needs to be - support had use set ours to 6GB because it kept crashing at 3Gb on incident matching. After setting it to 6Gb incident matching stopped crashing, I observed that it would regularly consume 4.5gb. See KA (KA363429 - unpublished) attached on set up of FTS in a server group - we use the "Alternative configuration" Regards, Andrew C. Goodall Software Engineer Development Services ago...@jcpenney.com jcpenney 6501 Legacy Drive Plano, TX 75024 jcp.com -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@arslist.org] On Behalf Of Jamie Sent: Wednesday, August 08, 2012 5:14 PM To: arslist@arslist.org Subject: Recommended size for FTS index collection directory Does anyone happen to know if there is any documentation/whitepaper on the recommended storage size for the FTS index collection directory in 7.6.04 might be? We are upgrading our currently system from 7.5 to 7.6.04 using BMC's staging method while keeping all of our proudction data. We have a total of 5 ARS servers in a server group and need to put the FTS idnex collection directory on a network drive so that they all can have access to run FTS if others fail (depends on server group ranking form). We have never used FTS before, so I'm uncertain where to begin on requesting storage for our network drive to hold the indexes. Below are some numbers for entris on our main forms, if it helps: INC: 566,983 CHG: 278,594 TSK: 71,322 PBI: 780 PKE: 284 Base Element: 490,828 RKM Articles (7.5): 8,539 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" FTS-Config-instructions.docx Description: FTS-Config-instructions.docx
Re: Recommended size for FTS index collection directory
Thanks for all of the information everyone. I figured base element was not available for FTS, but thought that would be the best way to show how many CIs we have in our system because it has all classes. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Recommended size for FTS index collection directory
One thing. I'm pretty sure base element or any CMDB items are not available for FTS. Sent from my iPhone On Aug 8, 2012, at 6:33 PM, Joe Martin D'Souza wrote: > There are no size recommendations published by BMC as this would really > depend on how much data would really go into FTS depending on your > customizations but based on the record count I think somewhere between 1 and > 2 TB's should be sufficiently adequate.. Most network disk drive capacities > these days fairly exceed these numbers so there's hardly a point in going > skimpy on this.. > > Just make sure that the shared network drive is highly available and the > network speed supporting it is the best you can get... > > Joe > > -Original Message- From: Gadgil, Abhijeet > Sent: Wednesday, August 08, 2012 6:21 PM Newsgroups: > public.remedy.arsystem.general > To: arslist@ARSLIST.ORG > Subject: Re: Recommended size for FTS index collection directory > > You are right. A shared network drive that can be written to from below > mentioned 5 machines needs to be available. > As far as I remember the documentation says, storage size should be 2 times > that data size that is being indexed > I think the 7.6.04 configuration guide calls that out > So really if you know what all you will end up indexing, you could > extrapolate that to provision the right size of the shared network drive > > Regards, > Abhijeet > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jamie > Sent: Thursday, August 09, 2012 3:44 AM > To: arslist@ARSLIST.ORG > Subject: Recommended size for FTS index collection directory > > Does anyone happen to know if there is any documentation/whitepaper on the > recommended storage size for the FTS index collection directory in 7.6.04 > might be? We are upgrading our currently system from 7.5 to 7.6.04 using > BMC's staging method while keeping all of our proudction data. We have a > total of 5 ARS servers in a server group and need to put the FTS idnex > collection directory on a network drive so that they all can have access to > run FTS if others fail (depends on server group ranking form). We have never > used FTS before, so I'm uncertain where to begin on requesting storage for > our network drive to hold the indexes. > > Below are some numbers for entris on our main forms, if it helps: > > INC: 566,983 > CHG: 278,594 > TSK: 71,322 > PBI: 780 > PKE: 284 > Base Element: 490,828 > RKM Articles (7.5): 8,539 > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Recommended size for FTS index collection directory
There are no size recommendations published by BMC as this would really depend on how much data would really go into FTS depending on your customizations but based on the record count I think somewhere between 1 and 2 TB's should be sufficiently adequate.. Most network disk drive capacities these days fairly exceed these numbers so there's hardly a point in going skimpy on this.. Just make sure that the shared network drive is highly available and the network speed supporting it is the best you can get... Joe -Original Message- From: Gadgil, Abhijeet Sent: Wednesday, August 08, 2012 6:21 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Recommended size for FTS index collection directory You are right. A shared network drive that can be written to from below mentioned 5 machines needs to be available. As far as I remember the documentation says, storage size should be 2 times that data size that is being indexed I think the 7.6.04 configuration guide calls that out So really if you know what all you will end up indexing, you could extrapolate that to provision the right size of the shared network drive Regards, Abhijeet The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jamie Sent: Thursday, August 09, 2012 3:44 AM To: arslist@ARSLIST.ORG Subject: Recommended size for FTS index collection directory Does anyone happen to know if there is any documentation/whitepaper on the recommended storage size for the FTS index collection directory in 7.6.04 might be? We are upgrading our currently system from 7.5 to 7.6.04 using BMC's staging method while keeping all of our proudction data. We have a total of 5 ARS servers in a server group and need to put the FTS idnex collection directory on a network drive so that they all can have access to run FTS if others fail (depends on server group ranking form). We have never used FTS before, so I'm uncertain where to begin on requesting storage for our network drive to hold the indexes. Below are some numbers for entris on our main forms, if it helps: INC: 566,983 CHG: 278,594 TSK: 71,322 PBI: 780 PKE: 284 Base Element: 490,828 RKM Articles (7.5): 8,539 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: Recommended size for FTS index collection directory
You are right. A shared network drive that can be written to from below mentioned 5 machines needs to be available. As far as I remember the documentation says, storage size should be 2 times that data size that is being indexed I think the 7.6.04 configuration guide calls that out So really if you know what all you will end up indexing, you could extrapolate that to provision the right size of the shared network drive Regards, Abhijeet The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jamie Sent: Thursday, August 09, 2012 3:44 AM To: arslist@ARSLIST.ORG Subject: Recommended size for FTS index collection directory Does anyone happen to know if there is any documentation/whitepaper on the recommended storage size for the FTS index collection directory in 7.6.04 might be? We are upgrading our currently system from 7.5 to 7.6.04 using BMC's staging method while keeping all of our proudction data. We have a total of 5 ARS servers in a server group and need to put the FTS idnex collection directory on a network drive so that they all can have access to run FTS if others fail (depends on server group ranking form). We have never used FTS before, so I'm uncertain where to begin on requesting storage for our network drive to hold the indexes. Below are some numbers for entris on our main forms, if it helps: INC: 566,983 CHG: 278,594 TSK: 71,322 PBI: 780 PKE: 284 Base Element: 490,828 RKM Articles (7.5): 8,539 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
