ivandika3 commented on PR #4585: URL: https://github.com/apache/ozone/pull/4585#issuecomment-1643367347
Hi @devmadhuu, thank you for checking. I'm currently still preoccupied with other matters so I haven't managed to revisit this feature. Regarding the pagination solution, currently Recon uses `prevKey` and `limit` to implement the pagination. However, my concern is that the Recon pagination framework is quite different from what is expected in the UI (antd table). For example, the UI sort by attribute mechanism (e.g. bucket usedBytes) will not work since it's done in memory and it's limited by the data returned by the backend. The UI index-based pagination framework is expected in the UI is more akin to JPA framework's `Pageable` (and `Sortable`), but integrating this might involve a very large change on the current Recon API since RocksDB does not currently have some of the capabilities. Hence, currently, we can have a drop down that will set the `limit` parameter and initialize it to a good default (e.g. 5000) to bound the number of buckets/volumes fetched. In our cluster, we only have 1000 - 2000 buckets we have not encountered the memory issue yet. Please let me know if you have any other suggestions regarding this. I can try to pick this up again in the next few days. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
