-
Notifications
You must be signed in to change notification settings - Fork 990
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
gRPC error on get_online_features
(NOAUTH authentication required)
#2285
Comments
Also probably worth mentioning that I still get this error with Redis Version 6.0. EDIT: |
any reason you're using the older version of Feast? Is it because you want a Spark based ingestion? |
@adchia that's correct. Also the helm chart we are using to install Feast on aks (azure kubernetes service) relies on deprecated installation strategy, unless there is a recommended approach for installing on third party Kubernetes service providers (i.e. other than google and aws). We are also running Kubeflow on our cluster so would like feast to be accessible internally for retrieving the historical and online features. |
Was able to make some headway by specifying
Not sure if the adaptive refresh is supposed to handle a new primary with new IP in this scenario. EDIT: Looks like After configuring the |
This was merged in. Mind adding a PR that ports the fix into the main repo too? |
Expected Behavior
get_online_features
should return the correct result:Current Behavior
Getting a gRPC error when calling
get_online_features
which points to an issue infeast-online-serving
.Materialization features is already completed and redis keys are present in redis store (
offline_to_online_ingestion
).Calling
get_online_features
works initially afteroffline_to_online_ingestion
, but not predictably in a standalone script.Error:
Error in
feast-online-serving
pod logs:Steps to reproduce
Install helm chart on AKS v1.22:
https://github.com/Azure/feast-azure/blob/rijai/feastchart/cluster/setup/feast-0.9.5-helmchart/README.md
Update
feast-onilne-serving
deployment image to use latest image tag which supports auth (0.26.3):feast-dev/feast-java-old#43
Set
feast-release-feast-online-serving
configmap to use external redis:Define
FeatureTable
and runoffline_to_online_ingestion
, then in a separate script runget_online_features
.Specifications
Possible Solution
Instead of relying on auto-discovery feature of lettuce.io redis client, use
RESP2
protocol on lower versions of Redis.redis/lettuce#1543 (comment)
Tried making a change in
RedisClient.java
:However I run into the following issue at runtime:
The text was updated successfully, but these errors were encountered: