I'm getting low memory warnings on the tserver, and the client dies with an OutOfMemory error when trying to close a writer.
I flush and close the writer basically after every change. On Thu, Aug 2, 2012 at 1:49 PM, William Slacum < [email protected]> wrote: > Is it the TServer bombing out or your client or both? How often are you > flushing your writer? > > > On Thu, Aug 2, 2012 at 10:34 AM, Matt Parker <[email protected]>wrote: > >> for my small test case, I'm storing some basic data in three tables: >> >> nodes - spatial index (id, list of child nodes, whether it's a leaf node ) >> image metadata - (id, bounding box coordinates, a text string of the >> bounding box) >> link - linking table that tells which images correspond to specific nodes. >> >> The image data isn't being stored in Accumulo, yet. >> >> >> >> On Thu, Aug 2, 2012 at 1:25 PM, Marc Parisi <[email protected]> wrote: >> >>> are you using native maps? if so, are they being used? >>> >>> >>> On Thu, Aug 2, 2012 at 1:16 PM, Matt Parker <[email protected]>wrote: >>> >>>> I setup a single instance Accumulo server. >>>> >>>> I can load 32K rows of image metadata without issue. >>>> >>>> I have another set of routines that build a dynamic spatial index, >>>> where nodes are inserted/updated/deleted over time. >>>> These operations are typically done one at a time, where each >>>> batchwriter are closed after use. >>>> >>>> It loads maybe a couple hundred operations, and then it dies with an >>>> OutOfMemory error when trying to close a batchwriter. >>>> >>>> I tried uping the memery settings on my client and on the tserver, but >>>> the results were the same. >>>> >>>> Outside of Accumulo, I can build the whole index in memory without any >>>> special JVM memory settings. I was wondering whether anyone else had run >>>> into a similar issue? >>>> >>> >>> >> >
