BatchGetObjects Error: BIN_NAME_TOO_LONG or maximum bin names are exceeded

[azamshaikh-ai]

Recently upgraded to AS 7 community edition and accordingly updated client to /v7 as well in my low latency app. I didn't have to change call to get Keys etc however I am getting following error in BatchGetObjectCall

Error in BatchGetObjects ResultCode: BIN_NAME_TOO_LONG, Iteration: 0, InDoubt: false, Node: xxxxxx812 127.0.0.1:3000: Bin name length greater than 15 characters, or maximum number of unique bin names are exceeded

Same call works with client /v7 and AS 6.4 Community edition without any issue. I tired to run show bins which resulted in 98 rows and none of them have bin namelength > 15, A few though has 14 as it was mentioned to be upper limit for bin names.

Though show bins command doesn't work in AS 7.

What could be done here to identify and fix the issue.

[khaf]

Sorry for my (extremely) late reply, this question has completely escaped me. Note that the name length can be maximum 15 Bytes, not runes, which may be longer than that.

I will add name length checks to the current version of the client (v8), where you will be able to run your program and get proper errors regarding the bin length limits.

[khaf]

I have added this feature in the v8.1.0 release. Since v8 is mostly compatible with v7, you can compile your code and see which bin is causing the issue.

[azamshaikh-ai]

Well I had forgot that I had raised the issue with client and as I had mentioned v6.4 works OK however there are random issue with client policy pool exhaustion in client v5 and for me >v5 of client were just leaking memory. (So server v6.4 and client v5 is my current working code despite the burst pool error)

I will try out v8 now to see how it will behave.

Thanks for you attention to the issue, Finally.

[khaf]

Did you manage to resolve this issue?