Bug 1929211 - Failed to parse 'writeOps' value 'XXXX' to integer: For input string: "XXXX"
Summary: Failed to parse 'writeOps' value 'XXXX' to integer: For input string: "XXXX"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh
Version: 4.4.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.6
: ---
Assignee: Shirly Radco
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On: 1928188
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 13:34 UTC by Shirly Radco
Modified: 2021-06-21 11:13 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-dwh-4.4.6.3
Doc Type: No Doc Update
Doc Text:
Clone Of: 928188
: 1973570 (view as bug list)
Environment:
Last Closed: 2021-06-18 07:54:44 UTC
oVirt Team: Metrics
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 113495 0 None MERGED Change IOPS data from Int to bigint 2021-04-22 13:21:11 UTC

Description Shirly Radco 2021-02-16 13:34:41 UTC
This bug was initially created as a copy of Bug #1928188

I am copying this bug because: 

It also affects DWH data collection and processing. Once the engine db is updated, we should also fix the dwh db and process.

Description of problem:
engine.log is flooded with messages of this kind. All values look greater than Integer.MAX_VALUE

~~~
2021-02-12 04:57:12,979+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] Failed to parse 'writeOps' value '3930677226' to integer: For input string: "3930677226"
2021-02-12 04:57:19,508+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-38) [] Failed to parse 'readOps' value '8116138202' to integer: For input string: "8116138202"
2021-02-12 04:57:19,974+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-36) [] Failed to parse 'writeOps' value '2771677512' to integer: For input string: "2771677512"
2021-02-12 04:57:19,974+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-36) [] Failed to parse 'writeOps' value '5088569863' to integer: For input string: "5088569863"
2021-02-12 04:57:20,339+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-95) [] Failed to parse 'readOps' value '46185802590' to integer: For input string: "46185802590"
2021-02-12 04:57:21,435+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) [] Failed to parse 'writeOps' value '3141675359' to integer: For input string: "3141675359"
2021-02-12 04:57:21,436+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) [] Failed to parse 'writeOps' value '3628042759' to integer: For input string: "3628042759"
2021-02-12 04:57:21,552+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] Failed to parse 'writeOps' value '2284978555' to integer: For input string: "2284978555"
2021-02-12 04:57:22,223+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] Failed to parse 'readOps' value '6345688634' to integer: For input string: "6345688634"
2021-02-12 04:57:22,223+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] Failed to parse 'readOps' value '6147464429' to integer: For input string: "6147464429"
2021-02-12 04:57:22,224+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] Failed to parse 'readOps' value '6402747154' to integer: For input string: "6402747154"
2021-02-12 04:57:23,208+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-95) [] Failed to parse 'writeOps' value '3166448596' to integer: For input string: "3166448596"
2021-02-12 04:57:24,869+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-18) [] Failed to parse 'readOps' value '2299747062' to integer: For input string: "2299747062"
~~~

$ grep "Failed to parse" /var/log/ovirt-engine/engine.log|wc -l
51968

Some VMs report these high numbers:

~~~
# vdsm-client Host getAllVmStats

        "disks": {
            "vdb": {
                "readLatency": "1025106.39766", 
                "writtenBytes": "22041295298048", 
                "writeOps": "753416638", <-----------
                "apparentsize": "1071594340352", 
                "readOps": "7324395556", <-----------
                "writeLatency": "889729.787007", 
                "imageID": "cc25e611-bfdf-46be-8c25-f67a46a7cf1e", 
                "readBytes": "97406204247040", 
                "flushLatency": "223080.341074", 
                "readRate": "12150237.8667", 
                "truesize": "1071594340352", 
                "writeRate": "4725589.33333"
            },
~~~

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.3.12-0.1.el8ev.noarch

How reproducible:
Constantly in customer environment with flash storage. I haven't reproduced it locally because it needs a high performance storage.

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:


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