Potential Concerns in Stopping Meteor Ungracefully -


just getting meteor, many accounts seems great project. 1 potential issue (which may not be) there doesn't seem meteor stop or programmatic way shut down meteor gracefully. please let me know if wrong this!

are there potential concerns maintaining database integrity (for example), if interrupt process using ctrl-c or shutting down via activity monitor? , there steps can take reduce or eliminate such issues?

caveat: recognize above questions vague, , understand considered harmful on stack, hope still answerable ones.

thanks,

it there cleanup takes place before process terminated (https://github.com/meteor/meteor/blob/master/tools/cleanup.js).

the first signal sent sigint polite way ask process shut down (and give time finish last running thread)

with database integrity, mongod process tries clean before shuts down & has recovery mechanism (from journal files) on quick recovery while restarting if forced shutdown.

that being said, in middle of longer running thread i'm not sure if it's allowed finish or killed immediately. meteor attempt give chance have graceful termination @ first, , escalates sighup sigterm (which still graceful termination signal). @ no point meteor force or send sigkill or sigstop.

so meteor apps should safe ctrl+c termination. activity monitor termination depends on type of signal sent (i.e force quit or quit)


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -