You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@fluo.apache.org by GitBox <gi...@apache.org> on 2017/12/30 02:51:04 UTC

[GitHub] alanblueshift commented on issue #991: Create 'fluo remove' command

alanblueshift commented on issue #991: Create 'fluo remove' command
URL: https://github.com/apache/fluo/issues/991#issuecomment-354523513
 
 
   I started to implement this doing the same thing the _init -f_ does but without the init part. 
   But I was wondering what happen if I remove the tables and the zookeeper data without stop the oracle and the workers before. Maybe apply the same validation of the _init_ command:
   
   ```java
   if (admin.applicationRunning()) {
       System.err.println("Error - The Fluo '" + config.getApplicationName() + "' application"
           + " is already running and must be stopped before running 'fluo init'. "
           + " Aborted initialization.");
       System.exit(-1);
   }
   ```
   
   OR we could store the PID of the workers and oracle in a file like .[APP_NAME]_**woker01**.pid, .[APP_NAME]_**worker02**.pid, APP_NAME]_**oracle01**.pid.... and when a remove command it is called if a **--force** flag we could find and kill this processes too.
   
   And... If we have the PID files we could implement commands like:
   ```shell
   fluo worker -a myapp -k
   fluo worker -a myapp -k
   ```
   AND 
   ```shell
   fluo worker -a myapp --kill
   fluo worker -a myapp --kill
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services