Victoriametrics: unexpected not match regex result

[mxlxm]

Describe the bug
not match regex returned unexpected result.
To Reproduce
container_memory_usage_bytes{container_name!~"|POD"}
got unexpected metrics with label container_name=""
Expected behavior
only return metrics with label container_name != "" AND container_name != "POD"
Version
master

[valyala]

Confirmed the bug. Temporary workaround is to use separate label matchers:

container_memory_usage_bytes{container_name!~"POD",container_name!=""}

[valyala]

The bug must be fixed in the commit ae1cc0fc4b81a2392e2701ca24ead55f2fd9818a .
@mxlxm , could you build VictoriaMetrics from this commit according to these instructions and verify whether everything works as expected?

[mxlxm]

tested, but the bug still exists.

query: container_memory_usage_bytes{container_name!~"|POD"}
still got unexpected result with label container_name="",while, actually those metrics doesn't have this label.

./vmstorage -version
vmstorage-20200611-070747-heads-cluster-0-g35191d84

[mxlxm]

BTW, here's another bad news.
After upgrade the whole cluster from v1.34.9 to head cluster with default replicationFactor, all data been rerouted to a certain vmstorage, then some query may cause vmstorage OOM, after OOM reroute to next vmstorage, repeatedly.

Rollback to v1.34.9, the cluster works as expected.

[valyala]

tested, but the bug still exists

The bug must be fixed in the commit 5f3a895c239cee1a0359866e4da57fe69cfa4ad4 .

After upgrade the whole cluster from v1.34.9 to head cluster with default replicationFactor , all data been rerouted to a certain vmstorage,

Confirmed the bug. It must be fixed in the commit 464682f380501b87555f7f280ba5006d4d60a373 .

[valyala]

FYI, all the bugfixes mentioned above are included in VictoriaMetrics v1.37.1.

[mxlxm]

I'll verify this on weekend, a little busy today.
Thanks again.