On 5/6/2018 3:09 PM, Atita Arora wrote:
I am working on a developing a utility which lets one monitor the
indexPipeline Status.
The indexing job runs in two forms where either it -
1. Creates a new core OR
2. Runs the delta on existing core.
To put down to simplest form I look into the DB timestamp when the indexing
job was triggered and have a desire to read some stat / metric from Solr
(preferably an API) which reports a timestamp when the CORE was created /
modified.
My utility completely relies on the difference between timestamps from DB &
Solr as these two timestamps are leveraged to determine health of pipeline.

I see the Master Version Timestamp under each shard which details the
version / Gen / Size.
Is that what I should be using ? How can I grab these from API ?
I tried using metrics api :
*http://localhost:8983/solr/admin/metrics?group=core&prefix=CORE
<http://localhost:8983/solr/admin/metrics?group=core&prefix=CORE>*
which details *CORE.startTime *but this timestamp changes whenever data is
being added to any core on this node.
*Is there any other suggestion to use some other way to determine the core
creation timestamp* ?

The startTime value is the time at which Solr started the core.  If that is getting updated frequently, then a reload operation is probably happening on the core.  Or, less likely, the Solr instance has been restarted.  I have checked a 6.6 system and on a core that is getting updates as frequently as once a minute, startTime is a couple of days ago, which was the last time that core was reloaded.

I've been trying to figure out whether a Lucene index keeps track of the time it was created, but I haven't found anything yet.  If it doesn't, I do wonder whether there might be some kind of metadata that Solr could write to the index to record information like this.  Solr would always have the option of writing such metadata to an entirely different location within the instanceDir.  The index creation time is probably not the only information that would be useful to have available.

Thanks,
Shawn

Reply via email to