chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <>
Subject [jira] Updated: (CHUKWA-446) Refactor tools/init.d scripts
Date Wed, 24 Feb 2010 23:01:29 GMT


Eric Yang updated CHUKWA-446:

    Attachment: CHUKWA-446-2.patch

The new chukwa command looks like this:


Usage: chukwa [--config confdir] COMMAND
where COMMAND is one of:
  agent         run a Chukwa Agent
  archive       run the Archive Manager
  collector     run a Chukwa Collector
  demux         run the Demux Manager
  dp            run the Post Demux data processors
  hicc          run a HICC Webserver
  droll         run a daily rolling job (deprecated)
  hroll         run a hourly rolling job (deprecated)
  version       print the version
  backfill      run a back fill data loader utility
  dumpArchive   view an archive file
  dumpRecord    view a record file
  tail          start tailing a file
Most command print help when invoked w/o parameters.


> Refactor tools/init.d scripts
> -----------------------------
>                 Key: CHUKWA-446
>                 URL:
>             Project: Hadoop Chukwa
>          Issue Type: Improvement
>            Reporter: Bill Graham
>            Assignee: Eric Yang
>         Attachments: chukwa, CHUKWA-446-2.patch, CHUKWA-446.patch
> 1. The scripts try to write lock files to /var/lock/subsys, which is owned by root. We
should change this location to be somewhere that doesn't require root access.
> 2. The actual run command does an su to the CHUKWA_USER which also caused problems for
us. It seems like it would be cleaner to not embed the su calls in the script, but instead
allow the user to su when they run the script (which worked much better for us). That way
everything done by the script would be done by the same user.
> 3. Each script has CHUKWA_HOME, CHUKWA_CONF_DIR and CHUKWA_USER hard coded. Hard coded
defaults is ok, but the ability to override them without modifying the scripts would be ideal.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message