LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi,

Has anyone implemented thread pools on the Enterprise Server. Just wanted to get some input from users to look at the value they achieved from it. As our Lavastorm use is vastly expanding i'm looking at options to logically partition pool areas depending on the functional area.

For example a large amount of our processes are for finance, but we now have Revenue Assurance, Back Office and Some Engineering Pieces I'd like to give lower priority too (if possible) or at least a smaller thread pool.

Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Wayne, I know a few of our customers have definitely used pooling to help balance use and workload. It has been used to ensure that scheduled graphs run as they should, and ad-hoc users don't disrupt that processing. I don't have any specifics on how they set it up, but it does sound like your environment could make use of pooling to help balance the sharing. Is there any specific questions you have?

Cheers
Rich

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi Rich,

Thanks. I'll have a bash at looking how to setup and test out in our DEV environment and post back how I did it.

Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Rich,

There is references to ls.brain.server.drone.poolconfig and ls.brain.controller.pool which config file do they go in. The documentation is a little short on that information.

Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Are you looking in the Thread Limit Configuration doc? I have attached a version here...this talks about that property and the format of the pool config file. You create a pool file as described in this document, and the poolconfig property just points to it.

Cheers
Rich
Attachments:
Thread Limit Configuration.pdf

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi Rich,

Yes, this is the documentation I have. It fails to mention which configuration file requires this configuration to go in. Is it ls_brain.prop by any chance and then the configuration file is a file I create referenced in the ls_brain.prop?

A text search for the two parms reference in the document does not exist in any conf files we have today

Regards
Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Yes, you can put the prop in any of the processed .prop files, but really, it should go into ls_brain.prop (we should add a commented out one, sorry). You have it exactly right, you create a config file and just have that property point at it. I think there might be a sample config file in conf/brain/server/pool.config.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Thanks. I'll give it a bash

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi All,

I hope this helps anyone in the future. I won't take any credit to get this working other than typing the config - Bob and Rich from Lavastorm thank you
1. Edit ls_brain.prop file in your $LAE_HOME/conf/brain folder and set the following:

ls.brain.server.drone.poolconfig="/opt/software/lae/4.5.4/conf/brain/server/pool.config" - your folder maybe different than mine

2. Edit the pool.config file to your desired config, mine looks something like:

pool:bre
size:10
defaultgroup:users
end:bre

3. check your pool.config aligns with your passwd file. Example line from mine below:

users:group:members=brain,admins

Since my pool.config give access to group users. Members brain and admins will use this config

4. Restart Lavastorm (this had to happen for me) I am going to assume because of the ls_brain.prop change.

5. Connect to Lavastorm via BRE. I setup to connect with 15 threads. 10 Connected and 5 failed. Failures were with the message below:

15:55:48 - ERROR (no node specified) no drones available

Therefore, I have limited users Brain and Admin to the number of threads they can use.