jkosh44 commented on issue #530: Improve 'fluo list' command to print Fluo application start time URL: https://github.com/apache/fluo/issues/530#issuecomment-599239295 I know this issue is very old but I was just doing some work on fluo list and oracles/workers so I wanted to give it a look. I was looking at the proposed solution and I think it has the following problem. Imagine you start a worker at 10:05 and then you start an oracle at 10:15. If you call fluo list it will show that the application is running and the start time is 10:05. If you then stop the worker and call fluo list again, it will show that the application is still running but the start time has changed to 10:15. So for any application whenever the oldest worker/oracle is stopped the start time would change. Another possible solution I was thinking of was storing start time as metadata in a ZNode under the app's root path. However I think this is full of concurrency issues around starting and stopping oracle/nodes at the same time. Basically there would be no good way of dealing with the scenario where there is 1 worker/oracle up, and it is stopped around the same time another oracle/worker is started.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
