Nodes table do not display all nodes without filters

[bogdanfazakas]

Nodes cannot be displayed after reaching the 10k after lots of scrolling

[mihaisc]

@tom1145 status on this?

[bogdanfazakas]

@tom1145 can we find a solution to this on incentive backend so we do not have to update the { “index”: { “max_result_window”: 500000 } } value, updating this might not be enough we can reach these values in a certain amount of time
maybe we can fix it with scroll or smth

[tom1145]

I have this proposal that can help us with this issue.

We can create a function that:

1. Checks current max_result_window and index total count (already available in /nodes API pagination)
2. If index count + new nodes to be inserted in count > max_result_window:
   • Calculate new_size = current_count + new nodes to insert count + X% buffer (to be decided)
   • Update via /_settings API in the body

API References:
GET /status/_settings/index.max_result_window (check current limit)

PUT /status/_settings (update limit)
Body:
{
"index": {
"max_result_window": "new_size"
}
}

Let me know if you have any suggestions. Thanks!
@mihaisc @bogdanfazakas

[bogdanfazakas]

I have this proposal that can help us with this issue.

We can create a function that:

1. Checks current max_result_window and index total count (already available in /nodes API pagination)

2. If index count + new nodes to be inserted in count > max_result_window:

   • Calculate new_size = current_count + new nodes to insert count + X% buffer (to be decided)
   • Update via /_settings API in the body

API References: GET /status/_settings/index.max_result_window (check current limit)

PUT /status/_settings (update limit) Body: { "index": { "max_result_window": "new_size" } }

Let me know if you have any suggestions. Thanks! @mihaisc @bogdanfazakas

I would not invest time into this atm, if this seems to be the only viable option lets just update it manually until we find a better way.
I'm trying some things atm, and i'll keep you posted if i find another possible solution