#community-help

Resolving Memory and Null Value Errors

TLDR sahubar requests advice from Jason for a memory error and Kishore Nallan for null values in object arrays. They get advice but it doesn't solve their problem.

1mo

Join the chat

Oct 24, 2023 (1 month ago)

Photo of md5-41ca8b93efee2249950bdd80b036a9dc

sahubar

12:49 PM

Hi Jason / Kishore Nallan

Can you confirm if the exact error message is "ObjectUnprocessable: Request failed with HTTP code 422 | Server said: Rejecting write: running out of resource type: OUT_OF_MEMORY"?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

02:02 PM

You would have to upgrade the cluster’s memory by going to Cluster Configuration > Modify to fix this error.

Oct 25, 2023 (1 month ago)

sahubar

06:38 AM

ok, Jason, We are currently using a 0.5GB RAM staging environment. Can you recommend an appropriate memory size?

10:10

sahubar

10:10 AM

Jason / Kishore Nallan "How should I handle null values in an array of objects? I'm encountering errors related to this issue
example error:
"RequestMalformed: Request failed with HTTP code 400 | Server said: Field prices.max.endDate must be an array of string."

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

10:21 AM

Null values must be marked as optional in the schema

10:22

Kishore Nallan

10:22 AM

As for memory usage, if you are just hitting into limit sometimes, a move to the next plan will be sufficient.

sahubar

10:27 AM

Could you please send me the attribute tag?
example my schema params:


    {
      "facet": true,
      "index": true,
      "infix": false,
      "locale": "",
      "name": "prices.max.endDate",
      "optional": true,
      "sort": false,
      "type": "string[]"
    }

Kishore Nallan

10:29 AM

Hmm that field is already set optional?

sahubar

10:30 AM

Yes, but I encounter an error when updating documents if prices.max.endDate is null at that time.

Kishore Nallan

10:31 AM

Please share a reproduceable code snippet that we can try running to replicate the issue.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Troubleshooting Import API Errors in Typesense

Atul was having trouble with import API errors, which Jason suggested might be due to a bug or missing fields. Upgrading solved the import issue but led to new problems with schemas and facet attributes.

1mo

Trouble with Document Error in Indexing

Hauke is encountering an error during indexing with a specific field and working to provide Kishore Nallan with a reproducible example. Kishore Nallan gave troubleshooting advice, but issue not yet resolved.

3mo

Handling Collection Errors in HA Clusters

Mischa was encountering random collection existence errors when updating schemas in a HA cluster. Jason suggested waiting between deletions and recreations or using an alias for zero downtime switches.

2mo

Issue with Embedding Error in Version 0.25.0.rc63

Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.

3mo

Resolving Embedding Distance Threshold Error Query Using '*'

Walter was having trouble using the embedding distance threshold which gave out an error with a '*'. Kishore Nallan clarified the issue and suggested a solution. Jason also provided a link to help dynamically set typesense-instantsearch-adapter parameters for future inquiries. The issue was resolved by their inputs.

1mo