Question about process.start/stop - what processes effected

Hi,

I was asked by the senior system administrator today about the process.start/stop/restart request handlers and whether they start/stop the actual java processes, or if not those, what. I traced the code through to the Process LLNode (which has a few subtypes, search being among them). There it makes the call to the AdminService drop-in to start or stop the process. Is this starting/stopping the various java procs that search spins up? If so, which ones?

Thanks in advance

-Hugh

Find more posts tagged with

Comments

Steve Brezina

Hi Hugh,

The short answer is that the request handlers act on the process DAPINode identified by nodeId parameter.

The Admin Server process API is SystemObj:LLStreamNode:Process. Memcached, the Java search grid, and various others implement it. Open an Admin Server object to see the processes listed. It is all the processes modeled in the System Volume.

Start / stop operations performed on the Update Distributor and Search Federator will similarly affect their child processes (Index Engine(s), Search Engine(s) respectively).

Steve

HFCDev

Thanks, Steve. When the process is "started" and it shows up as Scheduled but not running, what is it that happens to change its state from Scheduled to Running?

Also, and maybe I'm asking for too many trade secrets here, but behind the scenes, is the Admin Server doing an RMI call to either spin up a new Java executable or interacting with an already running process? We're on CS 10.0 U 2016-06, and I understand there was some changes in 10.5 as to how the admin servers access processes.

-Hugh

Steve Brezina

Hi Hugh,

Look at the specific info tab of the process in question - there is admin help describing the controls. Most processs show the command line and a schedule section among other configuration options.

The search related Java proceses are started by named executables in the bin dir (no RMI). Those process don't display the command line in the UI, but they're visibile in the Windows task manager.

Different processes have different start option radio buttons in the schedule section, if it's configurable. Manual processes start immediately. Interval and scheduled processes don't start immediately, but resume the configuration (to start in the future).

Steve

Shawn_Miller

>what is it that happens to change its state from Scheduled to Running?The time at which the process is scheduled to start goes by.Look at the 'Start Options' section for the process on Specific Info page.Later,ShawnOn 11/23/2016 1:31 PM, eLink Entry: Content Server Development Forum wrote:> *re Question about process.start/stop - what processes effected * Posted by Ferguson, Hugh On 11/23/2016 01:29 PM>>> Thanks, Steve. When the process is "started" and it shows up as Scheduled but not running, what is it that happens to change its state from Scheduled to Running?>> Also, and maybe I'm asking for too many trade secrets here, but behind the scenes, is the Admin Server doing an RMI call to either spin up a new Java executable or interacting with> an already running process? We're on CS 10.0 U 2016-06, and I understand there was some changes in 10.5 as to how the admin servers access processes.>> -Hugh>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> /[To post a comment, use the normal reply function]/> Topic: Question about process.start/stop - what processes effected > Forum: Content Server Development Forum > Content Server: Knowledge Center CS16 >