Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Y
YCSB
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Adnan Ahmad
YCSB
Commits
a6e1c636
Commit
a6e1c636
authored
9 years ago
by
Connor McCoy
Browse files
Options
Downloads
Patches
Plain Diff
[hbase] README updates
parent
45631e8b
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
hbase/README.md
+11
-7
11 additions, 7 deletions
hbase/README.md
with
11 additions
and
7 deletions
hbase/README.md
+
11
−
7
View file @
a6e1c636
...
...
@@ -17,11 +17,14 @@ mvn clean package
### 3. Create a HBase table for testing
```
/HBASE-HOME-DIR/bin/hbase shell
For best results, use the pre-splitting strategy recommended in
[
HBASE-4163
](
https://issues.apache.org/jira/browse/HBASE-4163
)
:
hbase(main):001:0> create 'usertable', 'family'
```
hbase(main):001:0> n_splits = 200 # HBase recommends (10 * number of regionservers)
hbase(main):002:0> create 'usertable', 'family', {SPLITS => (1..n_splits).map {|i| "user#{1000+i*(9999-1000)/n_splits}"}}
```
*Failing to do so will cause all writes to initially target a single region server*
.
### 4. Run the Workload
Before you can actually run the workload, you need to "load" the data first.
...
...
@@ -45,8 +48,9 @@ bin/ycsb run hbase -P workloads/workloada -cp /HBASE-HOME-DIR/conf -p table=user
```
## Configuration Options
Following options can be configurable using -p.
Following options can be configurable using
`
-p
`
.
*
clientbuffering : If true, buffer mutations on the client. The default is false.
*
writebuffersize : Buffer size to be used when clientbuffering is activated. The default is 12582912(= 1024
* 1024 *
12).
*
debug : If true, debugging logs are activated. The default is false.
*
`columnfamily`
: The HBase column family to target.
*
`clientbuffering`
: If true, buffer mutations on the client. The default is false.
*
`writebuffersize`
: Buffer size to be used when
`clientbuffering`
is activated. The default is 12MB.
*
`debug`
: If true, debugging logs are activated. The default is false.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment