FAQs and Troubleshooting #

FAQs about INFINI Gateway and handling methods are provided here. You are welcome to submit your problems here.

FAQs #

The Write Speed Is Not Improved #

Q: Why is the write speed not improved after I use bulk_reshuffle of the INFINI gateway?

A: If your cluster has a small number of nodes, for example, if it contains less than 10 data nodes or if the index throughput is lower than 15w/s, you may not need to use this feature or you do not need to focus on the write performance because the cluster size is too small and forwarding and request distribution have a minimal impact on Elasticsearch. Therefore, the performance does not differ greatly regardless of whether the gateway is used. There are other benefits of using bulk_reshuffle, for example, the impact of faults occurring on the back-end Elasticsearch can be decoupled if data is sent to the gateway first.

Common Faults #

Port Reuse Is Not Supported #

Error prompt: The OS doesn’t support SO_REUSEPORT: cannot enable SO_REUSEPORT: protocol not available

Fault description: Port reuse is enabled on INFINI Gateway by default. It is used for multi-process port sharing. Patches need to be installed in the Linux kernel of the old version so that the port reuse becomes available.

Solution: Modify the network monitoring configuration by changing reuse_port to false to disable port reuse.

     reuse_port: false

An Elasticsearch User Does Not Have Sufficient Permissions #

Error prompt: [03-10 14:57:43] [ERR] [app.go:325] shutdown: json: cannot unmarshal object into Go value of type []adapter.CatIndexResponse

Fault description: After discovery is enabled for Elasticsearch on INFINI Gateway, this error is generated if the user permission is insufficient. The cause is that relevant Elasticsearch APIs need to be accessed to acquire cluster information.

Solution: Grant the monitor and view_index_metadata permissions of all indexes to relevant Elasticsearch users.