Missing Records


(Jagmee) #1

I have import 4 set of data in one indices(DB), each set contain
10,00,000 records, first 3 set of importing data no issues. After the
4th importing Completed I saw 40,00,000 records in this DB and the
cluster health was ,"status":"red", "initializing_shards":2 ,
unfortunately I was stop the ES service. After the ES restart I see
only 30,96,990 records remaining 9,03,010 records missed. I have
checked all imports id finally I found the missing records were
founded in 4th set of Import .

  1. Is this problem raised due to Stopping of the ES Service at the
    time shards Initialization, if yes means how we can recover the
    missing records.
  2. If no means please let me what is the problem.

as mentioned below index & gateway details
index :
number_of_shards : 2
number_of_replicas : 0

Gateway type : FS

Version: ElasticSearch is 0.14.3

Thankyou


(Shay Banon) #2

Were there memory problems in the nodes? Did you see failures? Also, are you configuring the FS gateway on a shared file system that both nodes see?
On Saturday, February 26, 2011 at 9:35 AM, Jagmee wrote:

I have import 4 set of data in one indices(DB), each set contain
10,00,000 records, first 3 set of importing data no issues. After the
4th importing Completed I saw 40,00,000 records in this DB and the
cluster health was ,"status":"red", "initializing_shards":2 ,
unfortunately I was stop the ES service. After the ES restart I see
only 30,96,990 records remaining 9,03,010 records missed. I have
checked all imports id finally I found the missing records were
founded in 4th set of Import .

  1. Is this problem raised due to Stopping of the ES Service at the
    time shards Initialization, if yes means how we can recover the
    missing records.
  2. If no means please let me what is the problem.

as mentioned below index & gateway details
index :
number_of_shards : 2
number_of_replicas : 0

Gateway type : FS

Version: ElasticSearch is 0.14.3

Thankyou


(Jagmee) #3

There were no symptoms of memory problems, I have seen all 40,00,000
documents after indexing completed. Also, there was no failures.
I have configured the FS gateway in a shared location where both the
nodes can access it.
-- Jagmee

On Feb 27, 3:29 am, Shay Banon shay.ba...@elasticsearch.com wrote:

Were there memory problems in the nodes? Did you see failures? Also, are you configuring the FS gateway on a shared file system that both nodes see?

On Saturday, February 26, 2011 at 9:35 AM, Jagmee wrote:

I have import 4 set of data in one indices(DB), each set contain
10,00,000 records, first 3 set of importing data no issues. After the
4th importing Completed I saw 40,00,000 records in this DB and the
cluster health was ,"status":"red", "initializing_shards":2 ,
unfortunately I was stop the ES service. After the ES restart I see
only 30,96,990 records remaining 9,03,010 records missed. I have
checked all imports id finally I found the missing records were
founded in 4th set of Import .

  1. Is this problem raised due to Stopping of the ES Service at the
    time shards Initialization, if yes means how we can recover the
    missing records.
  2. If no means please let me what is the problem.

as mentioned below index & gateway details
index :
number_of_shards : 2
number_of_replicas : 0

Gateway type : FS

Version: ElasticSearch is 0.14.3

Thankyou- Hide quoted text -

  • Show quoted text -

(system) #4