[ https://issues.apache.org/jira/browse/ACCUMULO-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007853#comment-14007853 ]
ASF subversion and git services commented on ACCUMULO-2789: ----------------------------------------------------------- Commit f0dcf1e5570c12098e716ec58ea2f4bc3321053b in accumulo's branch refs/heads/1.5.2-SNAPSHOT from Bill Slacum [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=f0dcf1e ] ACCUMULO-2789 Added parameter to control the number of cells within a row When running the stress test, it is now possible to configure the writer to send mutations for rows that contain a random amount of column updates. This is controlled via the --min-row-width, --max-row-width and --row-width-seed parameters. I did some internal shuffling to make randomly generating numbers within a range more convenient. See the new RandomWithinRange class for details. > Add a system stress test based on key/cell/row size > --------------------------------------------------- > > Key: ACCUMULO-2789 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2789 > Project: Accumulo > Issue Type: Improvement > Components: test > Reporter: Sean Busbey > Assignee: William Slacum > Priority: Minor > Fix For: 1.5.2, 1.6.1, 1.7.0 > > > Add a system test that allows stress testing an Accumulo instance in the > presence of large cells and rows. > The test should run a configurable number of ingest and reading clients and > allow setting: > * configurable range of overall key size > * configurable range of key component sizes > * configurable value size > * configurable number of cells per row > * optional use of isolation on server and/or client > This kind of test would help us preemptively find issues like ACCUMULO-2671, > ACCUMULO-201, and the tserver memory crashes observed with some large > mutation sizes while working on YCSB support for Accumulo. > It will also help us provide test examples of supporting large cardinality on > rowids, column families, and visibilities. -- This message was sent by Atlassian JIRA (v6.2#6252)