accumulo native memory setting

["Ly, Kiet" <Ki...@finra.org>]

Has anyone used the native memory setting and found it stable enough for production used?  I found the data loading job crashed randomly after I turned it on. May be my setting was wrong elsewhere?

<property>
    <name>tserver.memory.maps.max</name>
    <value>4G</value>
  </property>

  <property>
    <name>tserver.memory.maps.native.enabled</name>
    <value>true</value>
  </property>

Confidentiality Notice::  This email, including attachments, may include non-public, proprietary, confidential or legally privileged information.  If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited.  If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately.  You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.

Re: accumulo native memory setting

["Ly, Kiet" <Ki...@finra.org>]

It turned out when the disks are filled 90%, Hadoop’s node manager declared the node is unusable and killed the bulk loader task. I am surprised the amount disk space it burned for +100 million triples. Nothing to do with Rya. ☺

On 1/18/17, 7:58 PM, "Josh Elser" <el...@apache.org> wrote:

    How did your data-loading job fail? This is a Accumulo server 
    configuration property -- it has no direct impact on your client.
    
    4G should be fine, just make sure that you have sufficient physical 
    memory on the Accumulo TabletServer hosts.
    
    Ly, Kiet wrote:
    > Has anyone used the native memory setting and found it stable enough for production used?  I found the data loading job crashed randomly after I turned it on. May be my setting was wrong elsewhere?
    >
    > <property>
    >      <name>tserver.memory.maps.max</name>
    >      <value>4G</value>
    >    </property>
    >
    >    <property>
    >      <name>tserver.memory.maps.native.enabled</name>
    >      <value>true</value>
    >    </property>
    >
    > Confidentiality Notice::  This email, including attachments, may include non-public, proprietary, confidential or legally privileged information.  If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited.  If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately.  You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.
    

Re: accumulo native memory setting

[Josh Elser <el...@apache.org>]

How did your data-loading job fail? This is a Accumulo server 
configuration property -- it has no direct impact on your client.

4G should be fine, just make sure that you have sufficient physical 
memory on the Accumulo TabletServer hosts.

Ly, Kiet wrote:
> Has anyone used the native memory setting and found it stable enough for production used?  I found the data loading job crashed randomly after I turned it on. May be my setting was wrong elsewhere?
>
> <property>
>      <name>tserver.memory.maps.max</name>
>      <value>4G</value>
>    </property>
>
>    <property>
>      <name>tserver.memory.maps.native.enabled</name>
>      <value>true</value>
>    </property>
>
> Confidentiality Notice::  This email, including attachments, may include non-public, proprietary, confidential or legally privileged information.  If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited.  If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately.  You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.