Recycling capability request for GeoEvent Extension

[AkihiroKURAKAKE]

GeoEvent Extension Manager should introduce settings to configure recycling or something similar function that ArcGIS for Server has.

Currently, the number of incoming GeoEvents is nothing but increasing, and there is no way to reflesh GeoEvent services without restarting manually those GeoEvent items (inputs, outputs, geoevent services or even GeoEvent Extension service itself).
Over long periods of time, resources with memory leaks could affect server throughput.

Considering the fact that GeoEvent Extension continuously juggles real-time processing, system needs to keep those services fresh, and this recycling function will be critical.

[AdamRepsher]

Depending on how you have your inputs and outputs set up, you need to then watch what this might affect.  This may cause a provider service or client to disconnect, and then need to be restarted.  I like the idea only IF there is an option to shut it off for specific active connectors.  

Hopefully I was able to describe that well enough from a non-developer or non-technical perspective.

[EricIronside]

While not OOTB for the GeoEvent Manager application, this sort of functionality can be accomplished using scripting and the GeoEvent Admin API. In addition to using the Admin API, you could use the scripting language to gracefully stop/start your GeoEvent Server periodically and/or based on certain thresholds (cpu, ram, disk, etc.).

Please see the following blog for examples on how this might be accomplished:

Scripting-tasks-using-the-geoevent-admin-api