Closes #210. Making sure maxLatency is not set to -1 by default. This ti...

...cket will be followed on by an API change to get rid of StoreConfig and use BatchWriterConfig and BatchScanConfig
Interesting- I'd be rather perplexed if this value alone were to drop your
ingest times. This refers to how long it takes idle mutations to get pushed
to the server. I'd see max memory lowering ingest speeds before max latency
would. Any reasoning behind your drops affected by max latencies would be
appreciated. I'm not necessarily worried about sticking to the defaults of
what Accumulo provides, I'm more interested in providing users with their
own reasonable defaults.


On Tue, Sep 2, 2014 at 2:18 AM, eawagner <notifications@github.com> wrote:

> In
> commons/src/main/java/org/calrissian/accumulorecipes/commons/domain/StoreConfig.java:
>
> > @@ -36,7 +36,7 @@ public StoreConfig() {
> >       * @param maxQueryThreads the number of concurrent threads to spawn for querying
> >       */
> >      public StoreConfig(int maxQueryThreads) {
> > -        this(maxQueryThreads, 10000, -1, 1);
> > +        this(maxQueryThreads, 10000, 10000, 1);
>
> I know with our testing or 5~10 second latencies we noticed a drop in
> ingest times. To be fair this wasn't thoroughly investigated, so it should
> be taken with a grain of salt.
>
> With this code however, it would be nice to either defend the reasoning
> behind choosing specific number or to default to the values used by the
> default underlying implementation (i.e. BatchWriterConfig).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/calrissian/accumulo-recipes/pull/215/files#r16971562>.
>