On Wed, Jun 3, 2015 at 11:28 AM, Vladimir Rodionov <vladrodionov@gmail.com>
wrote:
> >> Sounds like a possible
> >> workaround would have been to bump the value
> >> of hfile.index.block.max.size, did you try that?
>
> ? How is that?
>
I'm still looking into that, but I assume that Sathya would have tried to
bump that value in order to find that was the problem.
>
> -Vlad
>
> On Wed, Jun 3, 2015 at 11:03 AM, Esteban Gutierrez <esteban@cloudera.com>
> wrote:
>
> > Thats a very interesting finding Sathya. Could you please open an HBase
> > JIRA and additional information about this behavior? Sounds like a
> possible
> > workaround would have been to bump the value
> > of hfile.index.block.max.size, did you try that?
> >
> > thanks,
> > esteban.
> >
> > --
> > Cloudera, Inc.
> >
> >
> > On Tue, Jun 2, 2015 at 9:42 PM, sathyafmt <sathyafmt@gmail.com> wrote:
> >
> > > FYI: haven't seen this issue since we turned off tsdb compaction. See
> > > github
> > > opentsdb issue #490 <https://github.com/OpenTSDB/opentsdb/issues/490>
> > > for
> > > more info..
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-hbase.679495.n3.nabble.com/HBase-with-opentsdb-creates-huge-tmp-file-runs-out-of-hdfs-space-tp4067577p4072091.html
> > > Sent from the HBase User mailing list archive at Nabble.com.
> > >
> >
>
|