Keith Turner

Explore adding GitHub Actions test to ensure Uno can start Accumulo and Fluo

3

Adding smoke-test scripts to Uno that can run in TravisCI and verify Accumulo and Fluo start and work would be a really nice check to have for PRs. Not sure...

Look into geo-env

1

If we ever want to go the docker route with fluo-dev should look into https://github.com/pomadchin/geo-env I do like everything running natively for performance testing... not sure what performance would be...

Document minimum ram tested with

1

Would be nice to document in readme the minimum ram fluo-dev has been tested with. The minimum I have run fluo-dev on is a laptop w/ 8G. Not really sure...

Optimize Accumulo setting for Fluo

1

Need to optimize the Accumulo settings for fluo.

Explore placing automatically generated props in another file

2

Some ansible task modify the muchos props file. This could be surprising for a user that wishes to get repeatable performance from a config file. Also, there may be confusing...

I tried running 2 tablet servers per node and had to add the following to accumulo-site.xml. Would be nice to just add these. ```xml tserver.port.search true replication.receipt.service.port 10002-10009 ```

The property `twill_reserve_mem_mb` in `muchos.props` no longer works to configure reserved memory. Currently a Twill property is set in `yarn-site.xml` which needs to be removed. Could configure fluo-yarn to use...

Look into plotting disk I/O rates and network I/O rates

1

Currently the cluster stats plots CPU and load. It would be nice to plot disk I/O and network I/O rates also.

I setup a 10 node cluster and forgot to annotate a node for Fluo before running setup. So I annotated a node with fluo and ran setup again. After this...

Now that [ACCUMULO-2388](https://issues.apache.org/jira/browse/ACCUMULO-2388) is fixed, should be able to drop the following from accumulo-site.xml : ``` xml general.rpc.timeout 240s ```