TF_SIGNATURE_DEF is not used when selected on service startup

Description Context: Trying to load a tensorflow saved model which has multiple signature definitions.

Problem: The signature definition selected is not used. This happens randomly, when loading the container multiple times different signature definitions will be used even If TF_SIGNATURE_DEF has been set.

I see the log messages below when this happens.

2022-08-10 14:46:32.003735: W triton/tensorflow_backend_tf.cc:998] unable to find serving signature 'serving_default
2022-08-10 14:46:32.003743: W triton/tensorflow_backend_tf.cc:1000] using signature 'random_sig_def'

From looking at the code it seems like it falls into this section and chooses a signature def at random? But as I set the signature def in the config file id expect that block of code not to be executed?

Triton Information Triton version: 22.07-py3

This is the triton docker container.

To Reproduce I load in a model which has multiple signature definitions, this model has three.

I created a config.pbtxt which looks like the following, I played around with this config for a while I added all the relevant inputs and outputs to but the same outcome.

platform: "tensorflow_savedmodel"  
parameters: {
key: "TF_SIGNATURE_DEF"
value: {
  string_value: "sig_def_one"
  }
}

The model is a tensorflow saved model which has three signature definitions of which all have different inputs and outputs. (I can’t provide the model here). When I run saved_model_cli show --dir ./model --tag_set serve I am able to see all sigature definition.

Expected behavior

I’d expect TF_SIGNATURE_DEF to be used when loading the models.

[jbkyang-nvi]

Hi @ShamariYoti it looks like it’s a bug on our end. Thanks for reporting! In the meantime, you can try to run with --disable-auto-complete-config to fix your issue

[ShamariYoti]

@jbkyang-nvi

Thanks I will give this a try, do you have a time frame on when this bug will be fixed and released?