GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  GUNGHO::PLUGIN::APOPTOSIS (3)

.ds Aq ’

NAME

Gungho::Plugin::Apoptosis - Stop Execution In Long-Running Processes

CONTENTS

SYNOPSIS



  plugins:
    - module: Apoptosis
      config:
        timeout: 86400 # Stop execution after 1 day



DESCRIPTION

Gungho is usually used in a environment where the processes survive a long time.

Sometimes this leads the application to consume too much memory - Yes, a memory leak! The memory leak can reside both in Gungho or your particular Provider/Handler logic. If you or I can fix it, good. But usually memory leaks are just darn hard to find, and you know your application won’t acquire that much garbage in, say, 1 day.

I this case you just want to stop the execution of your crawler, and perhaps replace it by another process.

This plugin takes care of killing the running crawler process after a certain amount of time. When it reaches the timeout specified in the config, then the global is_running flag is set to off. After this flag is off, Gungho will not dispatch any more requests, and waits for other states to finish, eventually leading it to stop.

At this point you can re-dispatch your crawler proceses the way you want to.

METHODS

    setup

    check_apoptosis

    is_time_to_die

Search for    or go to Top of page |  Section 3 |  Main Index


perl v5.20.3 GUNGHO::PLUGIN::APOPTOSIS (3) 2007-12-01

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.