[
https://issues.apache.org/jira/browse/HBASE-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313292#comment-15313292
]
Andrew Purtell commented on HBASE-12721:
----------------------------------------
Awesome. I launched an Ubuntu 14.04 EC2 instance and followed your instructions
to get 1 primary + 5 secondary up and running in just a few minutes:
{noformat}
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 2.0.0-SNAPSHOT, rcbb95cd3a9bf9a9f8558560ae58f4061a73f15a8, Wed Jun 1
18:29:24 PDT 2016
hbase(main):001:0> status
1 active master, 1 backup masters, 5 servers, 0 dead, 0.4000 average load
{noformat}
Before I ran your setup script I did use LVM to make all locally attached SSD
storage into a single volume, formatted as XFS, and made /var/lib/docker a
symlink pointing to a directory on this device.
Questions and/or suggestions for enhancements follow. Perhaps subtasks? I'm
happy to help out as I'm able. The main point of interest for me is how to
build 0.98 SNAPSHOT images and run the IT test suite as part of release manager
duties.
- How does one build and register different versions of HBase for launching by
build_cluster? Possible to add to a local library?
- Can we set up a library of HBase versions to test? 0.98, 1.1, 1.2, 1.3, and
master.
- Build_cluster should allow me to set Xms and Xmx, at least for regionservers.
If I start up a high memory instance I might want 8 GB heaps, etc.
- How would we use G1 instead of CMS? Bonus points for extra GC flag support
for Shenandoah.
- How would we use a different version of the JVM? (including a custom compiled
version)
- Let's add a script/wrapper that runs all of the IT tests. Extra credit if one
can optionally specify monkey type and policy on the command line.
> Create Docker container cluster infrastructure to enable better testing
> -----------------------------------------------------------------------
>
> Key: HBASE-12721
> URL: https://issues.apache.org/jira/browse/HBASE-12721
> Project: HBase
> Issue Type: New Feature
> Reporter: Dima Spivak
> Assignee: Dima Spivak
>
> Some simple work on using HBase with Docker was committed into /dev-support
> as "hbase_docker;" all this did was stand up a standalone cluster from source
> and start a shell. Now seems like a good time to extend this to be useful for
> applications that could actual benefit the community, especially around
> testing. Some ideas:
> - Integration testing would be much more accessible if people could stand up
> distributed HBase clusters on a single host machine in a couple minutes and
> run our awesome hbase-it suite against it.
> - Binary compatibility testing of an HBase client is easiest when standing up
> an HBase cluster can be done once and then different client source/binary
> permutations run against it.
> - Upgrade testing, and especially rolling upgrade testing, doesn't have any
> upstream automation on build.apache.org, in part because it's a pain to set
> up x-node clusters on Apache infrastructure.
> This proposal, whether it stays under /dev-support or moves out into it's own
> top-level module ("hbase-docker" would conveniently fit the existing schema
> :-)), strives to create a simple framework for deploying "distributed,"
> multi-container Apache HBase clusters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
