Previously, the data warehouse would assume that the engine was not running when all hosts registered in the engine were non-resposive because the engine would not update their data. This update introduces a data warehouse heartbeat job that lets the data warehouse know that the engine is active even when all hosts are in a non-responsive state. The heartbeat job functions by periodically updating the status in the database to notify the data warehouse that the engine is active. The interval for updating the heartbeat can be configured via engine-config using the DwhHeartBeatInterval variable.

(In reply to comment #4)
> (In reply to comment #3)
> > Eli, do we update the host stats table in this staution?
> >
> >
> >
> > Yaniv
>
> I see nothing in the code that blocks the Host stat updates when its status
> is not responding ...
Can it be that vdsm doesn't send stats for non responsive hosts or something in these lines?

(In reply to Yaniv Dary from comment #5)
> Can it be that vdsm doesn't send stats for non responsive hosts or something
> in these lines?
1 - VDSM is being polled (it doesn't send anything)
2 - none-responsive means there is no communication to the host
This has never stopped engine from updating the rest of the hosts stats
And DWH should not stop collecting data in those areas.
the scenario is easy to reproduce,
Yaniv can you please try reproducing on your environment ?

After discussing the issue with Yaniv,
This issue happens only when all hosts in the system are none-responsive.
Although less interesting, still this needs to be handled on the engine side regardless of the hosts statuses.
One option to solve it is to update a variable in dwh_history_timekeeping table everytime the engine start the polling from VDSM.
In the past we have tried doing that but we tried to use the same transactions used by the stats collection, which caused db locking issues.
The fact is that all the DWH needs is to understand that the engine is up.
So the most basic approach is simply to have a quartz job that function as heart beat and update the variable mentioned above, to enable DWH to understand that the engine is actually up and to produce a record for all hosts (even when none-responsive)
This Heart Beat frequency should be configurable in the vdc_options.

(In reply to Barak from comment #7)
> The fact is that all the DWH needs is to understand that the engine is up.
> So the most basic approach is simply to have a quartz job that function as
> heart beat and update the variable mentioned above, to enable DWH to
> understand that the engine is actually up and to produce a record for all
> hosts (even when none-responsive)
we discussed this when discussed bug#918039 comment#2...
I don't like blind watchdogs... but it is better than what we have anyway...

"ETL service sampling has encountered an error"
This error is also encountered if your language is not configured as "en_US.UTF8".
(For instance "en_GB.UTF-8")
Please see RHN support case 00898361 or speak to RH TSA Rui Gouveia for more details.
Thank You

Team,
I recently attached a case to this, however the customer is running the most up to date rhevm packages, and we verified the locale settings in the database (As per the KCS https://access.redhat.com/site/solutions/413393 - is there anything else I should checkm or maybe create a new bug? Thanks

(In reply to wdaniel from comment #14)
> Team,
>
> I recently attached a case to this, however the customer is running the most
> up to date rhevm packages, and we verified the locale settings in the
> database (As per the KCS https://access.redhat.com/site/solutions/413393 -
> is there anything else I should checkm or maybe create a new bug? Thanks
If you unsure open a new bug, attach logs, worse case your bug will be marked as duplicate of this or any other bug.

This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes
Thanks in advance.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2014-0038.html

Note

You need to
log in
before you can comment on or make changes to this bug.