Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPuHRiBru76XLhVPdHA_+rvVF_S3yZmmuHWjFA-ov4b3ugoVnQ@mail.gmail.com>
References: <CAPuHRiBru76XLhVPdHA_+rvVF_S3yZmmuHWjFA-ov4b3ugoVnQ@mail.gmail.com>
From: Suresh Prajapati <sureshpraja1234@gmail.com>
Date: Thu, 27 Apr 2017 16:47:01 +0530
Message-ID: <CAPuHRiDybAwFawo+7EO7K5ErdJD758crza3KqRgxU7G6VCvhdg@mail.gmail.com>
Subject: Fwd: Accumulo Table Sacanning Taking Time!!!
To: accumulo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=94eb2c047dca9f6a8d054e241884
archived-at: Thu, 27 Apr 2017 11:17:08 -0000

--94eb2c047dca9f6a8d054e241884
Content-Type: text/plain; charset=UTF-8

---------- Forwarded message ----------
From: Suresh Prajapati <sureshpraja1234@gmail.com>
Date: Thu, Apr 27, 2017 at 4:39 PM
Subject: Accumulo Table Sacanning Taking Time!!!
To: dev@accumulo.apache.org


Hello Team

I am developing a client in accumulo to store geo-spatial information and
using geomesa for indexing on top of it. However i found that scanning *~1
million* records taking *2-3 sec*. I looked at indexes and query plan of
geomesa but not able to find cause of the problem. I am running accumulo as
single tablet-server(including master). I want to know -
what are the factors can affect accumulo scanning operation? how can I
optimise this time?

Thank You
Suresh Prajapati

--94eb2c047dca9f6a8d054e241884--