Adam,
Take a look at this archive [1], which discusses the gc.trash.ignore
flag.
[1]
http://apache-accumulo.1065345.n5.nabble.com/Accumulo-GC-and-Hadoop-trash-settings-td14895.html
On Wed, Aug 9, 2017 at 11:14 AM, Adam J. Shook wrote:
> Hello all,
>
> Has there ever
Max,
Additionally, what are your max open files? If you are under heavy ingest
you may exceed this with compactions if they cannot keep up. Additionally,
how many files per compaction are you allowing?
On Thu, Mar 23, 2017 at 10:27 AM, Michael Wall wrote:
> Max,
>
> On you 3
Mike,
That's a good point. My thoughts on this are that we lack the utilities
to help since of the five largish instances I've seen recently have
required their maintainers to edit the metadata table manually. The
CheckForMetadataProblems could prompt the user with ways to fix certain
issues
if needed if someone else does not fill in my holey phone responses.
On Mon, Feb 27, 2017 at 8:47 PM, Marc P. <marc.par...@gmail.com> wrote:
> Matt,
> You can add replace/insert the key extents in which the hole exists. The
> check simply looks at the prev end row key ( ~
Matt,
You can add replace/insert the key extents in which the hole exists. The
check simply looks at the prev end row key ( ~pr ) and ensure it matches
the actual last end row. You can insert the keys for that extent. I would
back up the table just in case. I thought there was a utility to fill
Thanks for catching that! I did indeed write that down incorrectly. I
apologize. I'll fix that tonight.
Iterators are stacked based on their priority ( when you set them via
the scanner, for example ) or the input format's IteratorSetting.
The init method comment is a general suggestion, for
Why are you using that accepts the thrift key and range? They're
internal communication objects within accumulo. I haven't looked the
code directly, but they're likely contracted to be set in a different
manner.
On Tue, Jun 26, 2012 at 8:56 AM, David Medinets
david.medin...@gmail.com wrote:
I
I realized that Mr Slacum and I addressed the concern of using thrift;
however, perhaps you are doing something internally. Have you tried
setting the stop key on the TRange just for SGs?
On Tue, Jun 26, 2012 at 9:03 AM, Marc P. marc.par...@gmail.com wrote:
Why are you using that accepts
of should not be provided
for cf, cq, and visibility?
On Tue, Jun 26, 2012 at 9:09 AM, Marc P. marc.par...@gmail.com wrote:
I realized that Mr Slacum and I addressed the concern of using thrift;
however, perhaps you are doing something internally. Have you tried
setting the stop key on the TRange
It may also serve you to extend the appropriate aggregator, thereby
setting your source iter to the batch scanner's iterator. You can then
iteratate over the aggregated result set ( if possible ).
I haven't actually tried this, but you would be limited by memory at
the client ( depending on the
10 matches
Mail list logo