You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the first one, it takes the model store location from config; in the second, it ignores that in favor of the command line.
This command line fails (error message in the second line):
> torchserve --start --ts-config config_with_batch.properties --models d161good=d161good.mar
--model-store is required to load model locally.
Again the model store is specified, just not on the command line. TorchServe should check the config for missing parameters before rejecting a command line.
The text was updated successfully, but these errors were encountered:
Got it. Fallback to config properties when command line specifies incorrect properties.
IOW, this can be regarded as a "user override config failure". As in, user tried to override the config properties and passed incorrect configs. I'd argue that this is not a launch blocker, in fact, I would argue this is not a bug but requires a better error message.
Under those conditions, the following starts the server but fails to start workers (which is expected, because it is looking in the wrong folder for the model):
I have models in my
model_store
folder, and the linemodel_store=model_store
in myconfig.properties
file.The following two command lines work, with the first starting no endpoints and the second starting workers for the model:
In the first one, it takes the model store location from config; in the second, it ignores that in favor of the command line.
This command line fails (error message in the second line):
Again the model store is specified, just not on the command line. TorchServe should check the config for missing parameters before rejecting a command line.
The text was updated successfully, but these errors were encountered: