Opentsdb 2.4.1 does not create all TagV UID

[Alessandro PL]

I have a TSDB which does not load all elements in a 21MB Json file and does not create the relative UID for tagV.

CFG parameters are the following:

tsd.network.port = 4242
tsd.http.staticroot = /usr/share/opentsdb/static/
tsd.http.cachedir = /var/tmp/opentsdb
tsd.core.plugin_path = /usr/share/opentsdb/plugins
tsd.http.request.cors_domains = *
tsd.core.timezone = Europe/Rome
tsd.http.request.enable_chunked = true
tsd.storage.fix_duplicates = true
tsd.http.request.max_chunk = 37748736
tsd.core.meta.enable_realtime_ts = true
tsd.core.meta.enable_realtime_uid = true
tsd.storage.max_tags = 8
tsd.storage.uid.width.tagv = 5

In the log are present outputs like this:

11:21:29.666 INFO  [UniqueId.allocateUid] - Creating an ID for kind='tagv' name='sdcf'
11:21:29.667 INFO  [UniqueId.createReverseMapping] - Got ID=530 for kind='tagv' name='sdcf'
11:21:29.668 INFO  [UniqueId.done] - Wrote UIDMeta for: sdcf
11:21:29.668 INFO  [UniqueId.done] - Completed pending assignment for: sdcf

...

but NOT for tagValues like "sdbpk", even if it is an element inserted via http API.

Json file is like this:

"metric": "NMON.DISKBUSY",
"timestamp": 1655744231,
"value": 0.1,
"tags": {
  "nmobj": "sdbpk",
  "nmdskdmdev": "dm-34",
  "nmdsksize": "4.0T",
  "nmdsklunid": "360060e80087a410000507a4100000115",
  "nmdskname": "DGCDSXP022_B1297",
  "nmdskrport": "1.0.1.21",
  "host": "02srv00oaa"
  }

The Number of different tag values for all tagkeys present in the single Json file are the following:

[root@CENTOS8 LOAD]# for BB in nmobj nmdskdmdev nmdsksize nmdsklunid nmdskname nmdskrport host; do cat DNA.02srv00oaa.DISKBUSY.54.json|LC_ALL=C grep $BB|sort|uniq -c|wc -l|sed "s/^/$BB: /"; done
nmobj: 3750
nmdskdmdev: 123
nmdsksize: 6
nmdsklunid: 123
nmdskname: 123
nmdskrport: 3612
host: 1

Json size is the following:
[root@CENTOS8 LOAD]# ls -la DNA.02srv00oaa.DISKBUSY.54.json
-rw-r--r-- 1 root root 21211322 Jul 24 02:21 DNA.02srv00oaa.DISKBUSY.54.json

Is it possible that Opentsdb is not able to load all 71900 elements in a single Json loaded via Http api, and does not create 3750+123+6+123+123+3612 UIDs ?

If I extract from the Json the single elements with a specific value for "nmobj" and I load it again, the element is present in the DB and the UID is created correctly.

Thank you, I'll give more details if needed.

[一个股民的自我修养]

UID is shared in TSDB. Is it possible that "sdbpk" has been created an UID before so you didn't find the corresponding logs to the request.

Did the write succeed with 200?