OpenHistorian - Data GAP recovery option

Hi,

I’m testing data gap recovery option for Internal subscription. Data gap recovery request was issued from subscriber, but no data is arriving from publisher.

Please see the log details.
[4/14/2020 12:11:23 PM] [ABC-182] [DataGapRecoverer] Attempting connection to tcp://IPAddress:6175…
[4/14/2020 12:11:23 PM] [ABC-182] [DataGapRecoverer] Attempting command channel connection to publisher…
[4/14/2020 12:11:23 PM] [ABC-182] [DataGapRecoverer] Connection established.
[4/14/2020 12:11:23 PM] [ABC-182] [DataGapRecoverer] Data subscriber command channel connection to publisher was established.
[4/14/2020 12:11:55 PM] [ABC-182] [DataGapRecoverer] Starting data gap recovery for period “2020-04-14 02:04:29.629” - “2020-04-14 02:11:29.566”…
[4/14/2020 12:11:55 PM] [ABC-182] [DataGapRecoverer] Success code received in response to server command “Subscribe”: Client subscribed as compact unsynchronized with a temporal constraint.
[4/14/2020 12:12:07 PM] [ABC-182] 100,002 measurements have been processed so far…
[4/14/2020 12:12:15 PM] [ABC-182] [DataGapRecoverer] WARNING:
No data received in 10.0 seconds, canceling current data recovery operation…
[4/14/2020 12:12:15 PM] [ABC-182] [DataGapRecoverer] WARNING: Recovered 0 measurements for period “2020-04-14 02:04:29.629” - “2020-04-14 02:11:29.566”.
[4/14/2020 12:12:15 PM] [ABC-182] [DataGapRecoverer] Success code received in response to server command “Unsubscribe”: Client unsubscribed.

Can you please help on this?

Does the archive on the publisher system have data between 2020-04-14 02:04:29.629 and 2020-04-14 02:11:29.566?

I only enabled the reader adapter to be configured automatically in a recent build. Either will need to setup reader adapter manually, or install the nightly build.

Expecting a new official release of openHistorian this week.

Thanks,
Ritchie

Hi Ritchie/Stephen,

Thanks for your response. I checked the data availability for that gap period at publisher machine, data is available, but not publishing to subscriber. Please see the log details between publisher and subscriber for gap data recovery process.

Subscriber Log:

[4/15/2020 12:30:52 PM] [PUBLSIHER] [DataGapRecoverer] Starting data gap recovery for period “2020-04-15 02:25:37.259” - “2020-04-15 02:30:25.999”…

[4/15/2020 12:30:52 PM] [PUBLSIHER] [DataGapRecoverer] Success code received in response to server command “Subscribe”: Client subscribed as compact unsynchronized with a temporal constraint.

[4/15/2020 12:31:12 PM] [PUBLSIHER] [DataGapRecoverer] WARNING:
No data received in 10.0 seconds, canceling current data recovery operation…

[4/15/2020 12:31:12 PM] [PUBLSIHER] [DataGapRecoverer] WARNING: Recovered 0 measurements for period “2020-04-15 02:25:37.259” - “2020-04-15 02:30:25.999”.

[4/15/2020 12:31:12 PM] [PUBLSIHER] [DataGapRecoverer] Success code received in response to server command “Unsubscribe”: Client unsubscribed

Publisher Log:
[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] Initializing temporal session for host “SUBSCRIBER.COMPANY” spanning 2020-04-15 02:25:37.259 to 2020-04-15 02:30:25.999 processing data at 66ms intervals…

[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] Starting measurement route calculation…

[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] [All Adapters Collection#<SUBSCRIBER.COMPANY>@2020-04-15 02:25:37] Statistics reset for this collection.

[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] Calculated 77 routes for 1 destination in 4 milliseconds.

[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] Starting measurement route calculation…

[4/15/2020 12:30:51 PM] Starting measurement route calculation…

[4/15/2020 12:30:51 PM] [SUBSCRIBER.COMPANY] Calculated 77 routes for 1 destination in 0 seconds.

If you could provide suggestion to handle this issue, it would be great.

What is the “reader adapter”, do I need to enable it, please help.

Yeah, unless you install the nightly build you will need manually enable the “reader adapter”.

Go to “Inputs > Manage Custom Inputs” in the openHistorian UI Tool (not web):

If there is not an adapter called “PPAREADER”, click “Add New” and enter “PPAREADER” for the “Name” of the adapter. Select “openHistorian 2.0. (Local)” from the adapter “Type” list and paste the following in the “Connection Sting” field:

InstanceName=PPA; HistorianServer=127.0.0.1; ConnectOnDemand=true

This will setup the the openHistorian to automatically respond to temporal data subscriptions, i.e., allow the system to read history from GEP or STTP remote connections.

Otherwise the system would respond as you describe above.

Again, this adapter is automatically added for newer builds - but will have to be manually enabled for older builds.

Thanks,
Ritchie

Hi Ritchie,
Thanks for your quick response.
Data GAP recovery is working fine after configuring PPAREADER at publisher side.

Also please confirm,
Does “Data GAP Recovery” option work for “TLS” subscription (port 6177)?

Thanks & Regards
Logu

Hi Ritchie/Stephen,

My testing environment, “Data Gap Recovery” is working fine with TLS subscription (port 6177) as well as Internal subscription.

If you could confirm “Data Gap Recovery” option will work for both subscription from your end, it would be great to confirm to our customer.

Thanks & Regards
Logu

Should be fine on any subscription type.

Thanks!
Ritchie

Dear Ritchi,

I have raised a query, please kindly clarify.