|
It would be good to assign appropriate usages to pfsa-usr01, 02, and 03. pfsa-usr03 was bought primarily for intensive netflow use in the future operation, but could be used for some general cpu-bound jobs for now, too. pfsa-anXX are prepared for batch jobs, which is under configuration, so if you could manage your interactive jobs within the pfsa-usr0[1-3], that would be helpful for now. Yoshida, Hiroshige may comment on this.
|
|
I just want to underscore the fact that drpActor operation is fundamental to any drp/QA work in Hilo: it is the drpActor which ingests the raw data and immediately performs on-the-fly reductions of fresh data. In other words, it should be treated as an essential part of data reductions, and not as part of "interactive" or "development" work. I believe that we should settle on the right host for it.
|
|
As per discussion with Hisanori Furusawa last week, there are two possibilities:
- run drpActor on the master node of the cluster system (for longer run but keep thinking about using in the next run)
- run drpActor on pfsa-usr03 (netflow machine) as a backup plan
The technical issue of the file system of the cluster has been resolved (I believe), so we can move forward for the first possibility. After I get a full access to pfsa-usr03, I will work on the second possibility.
|