-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to provision iscsi volumes on truenas scale #67
Comments
StorageClass parameters:
|
Proof that truenas-csp pod can hit the API:
|
If I had to guess, your problem is here: If I manually run that API call, it takes about 25s to return. |
Thank you for reporting this. How many datasets (including snapshots) do you have? |
About 20 |
I did some adhoc curl'ing. In the current shape and form, one second is added to Using the |
Same truenas version? |
Dragonfish-24.04.2 |
Seems this will be its replacement: https://github.com/truenas/api_client |
That client performs the same api call in 17s. |
Regardless... your hypothesis is overall correct. I have two TrueNAS scale appliances. One this RESTful API call works fine as is. The other, it does not. Happen to know where on a TrueNAS scale box the restful api logs? Would be interesting to fully RCA this. |
Runtime of RESTful call at localhost:
|
Found it. Used democratic-csi before. It managed to make over 81000 snapshots of various things. Removed them all and now this api call returns even RESTful in under 7s. |
Yes, I've been served this notice and will replace my home cooked REST interaction with the websocket library.
Still seems very slow. |
Indeed. That, however, is an issue for iXSystems. I'll file a ticket over there. So it sounds like the path here is probably filters in a future release then websocket come 25.04 or maybe websocket first? |
The next release by the end of the year will have query option filters. This will most likely be the last RESTful release before switching to websocket but that has not been scoped yet. |
ElectricEel-24.10-RC.2
The text was updated successfully, but these errors were encountered: