Home » forums » General » Troubleshooting

Record not getting deleted from the index

Submitted by prkumar on Tue, 2010-02-02 13:35.Troubleshooting

Incemental indexing is not deleting the record from the index. It finds the record that should be deleted but terminates before updating the index. The log says "Running flag file not found. Process terminating".
What is running flag?

Following is fragment of log:

INFO 2010-02-02 15:12:55,009- 1 processed...
INFO 2010-02-02 15:12:58,024- 1814 processed...
INFO 2010-02-02 15:13:01,180- 3001 processed...
INFO 2010-02-02 15:13:05,367- 4001 processed...
INFO 2010-02-02 15:13:08,398- 6001 processed...
INFO 2010-02-02 15:13:09,960- Dir size:7,598,484 Bytes
INFO 2010-02-02 15:13:11,429- 7769 processed...
INFO 2010-02-02 15:13:14,444- 8085 processed...
INFO 2010-02-02 15:13:17,459- 10051 processed...
INFO 2010-02-02 15:13:20,474- 11894 processed...
INFO 2010-02-02 15:13:23,802- 13001 processed...
INFO 2010-02-02 15:13:24,255- 13300 documents to be processed.
INFO 2010-02-02 15:13:24,255- Comparing to find what's deleted ...
INFO 2010-02-02 15:13:24,458- Deleted size=1
INFO 2010-02-02 15:13:24,458- deleting 1 documents
WARN 2010-02-02 15:13:25,911- Running flag file not found. Process terminating...
INFO 2010-02-02 15:13:25,911- Stopping all threads...

login or register to post comments | previous forum topic | next forum topic

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Is there another indexing process going on?
Submitted by will on Tue, 2010-02-02 15:38.
Is there another indexing process going on? Running flag file is just one file to signal the indexing process to stop. Please let me know the version and build number if it always happens.
login or register to post comments
Records not getting deleted from the index
Submitted by prkumar on Tue, 2010-02-02 16:31.

I am using Version: 2.1.6(build 471).

There may be other indexing going on at the same time, since I have two seperate indexing jobs scheduled. But I have added following in quartz.propertie "org.quartz.threadPool.threadCount = 2". I hope both indexing processes are independent of each other.

login or register to post comments
one indexing process only for one index
Submitted by will on Tue, 2010-02-02 16:56.

I see. That's the reason. It is interfered by another indexing process of the same index.

If you set it to 2, for the whole DBSight instance, you can have two indexing processes. However, if you have two indexing processes for the same index at the same time, one of them will get stopped.

For the same index, you will need to schedule the indexing so that they are no possible overlapping time.

login or register to post comments
One indexing job for one index
Submitted by prkumar on Wed, 2010-02-03 07:38.

Well I think I did not make myself clear. There are two seperate indexes and each has only one indexing job scheduled at a difference of 5 mins.

login or register to post comments
too short between each incremental idnexing?
Submitted by will on Wed, 2010-02-03 16:28.

It could be that the intervals between each incremental indexing for one index is too short?

If too short, the latter indexing process could stop the previous one.

In general, leaving the quartz schedule to run only one process is safe.

You can send us your index configuration files and we can have a local test. dbsight at gmail dot com

login or register to post comments