1 / 5

BIGTOP

BIGTOP. Configuration and Wrapper Executable. Motivation. Overall, even with bigtop , still lack the feel of one product family Upstream modules have inconsistent configuration mechanism Too many environment valuables to set for each modules

aira
Download Presentation

BIGTOP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BIGTOP Configuration and Wrapper Executable

  2. Motivation • Overall, even with bigtop, still lack the feel of one product family • Upstream modules have inconsistent configuration mechanism • Too many environment valuables to set for each modules • Too many commands to remember to start various module daemons • No easy way to query daemon status • All or nothing for modules – cannot add/remove modules (??? – might be useful), maybe pulling down too much or too little.

  3. Proposal • Single BIGTOP_HOME environment to set • All other environment variables could be derived and set and listed for the user by convention. • Single executable “bigtop” for house keeping • Start/stop modules • List related settings, modules, ports, etc. • Install/remove bigtop modules

  4. What’s Not In Scope • Wrapping upstream module commands such as hadoop, mahout, pig, etc.

  5. Usage • export BIGTOP_HOME=/usr/lib/bigtop • /usr/bin/bigtop <options> • -h/-help – Help message, and link to bigtopGettingStarted web page • -list machines|daemons|ports|modules • -start • -stop • -add-machine <machine list> • -remove-machine <machine list> | all • -cluster sync-config|<cmd>– rsync configuration files, jar files across cluster machines • -clean – clean logs, caches across the cluster machines • -install <module> • -uninstall <module>

More Related