Thank you, Is there way to maintain that data locality, I mean over time with table splitting, hdfs rebalancing etc we may not have data locality…
Thanks again -S From: Christopher <ctubb...@apache.org> Sent: Friday, September 10, 2021 8:40 AM To: accumulo-user <user@accumulo.apache.org> Subject: [EXTERNAL EMAIL] - Re: accumulo and hdfs data locality Data locality and simplified deployments are the only reasons I can think of. Accumulo doesn't do anything particularly special for data locality, but typically, an HDFS client (like Accumulo servers) will (or can be configured to) write one copy of any new blocks locally, which should permit efficient reads later. This works well with Accumulo's hosting behavior, where each tablet is hosted on a single server solely responsible for its reads and writes. On Fri, Sep 10, 2021, 07:22 Shailesh Ligade <slig...@fbi.gov<mailto:slig...@fbi.gov>> wrote: Hello I am suing Hadoop 3.3 and accumulo 1.10. Does accumulo take advantage of Hadoop data locality? What are the other benefits of having tserver and datanode process on the same instance? -S
