gRPC unable to connect

Support
,
1

Description

We’ve been using HTTP just find but when trying to use the gRPC URL on Weaviate client 4.11.1, we get this error:

Unable to get client collection: 'NoneType' object has no attribute 'collections'

However, I saw in the documentation this:

image
image1428×182 25.3 KB

I’m a bit confused if it uses gRPC underneath the hood or whether we need to pass in the GRPC variable in the code:

client = weaviate.connect_to_weaviate_cloud(
		cluster_url=wcd_url,                                    # Replace with your Weaviate Cloud URL
		auth_credentials=wvc.init.Auth.api_key(wcd_api_key),    # Replace with your Weaviate Cloud key
	)

Server Setup Information

  • Weaviate Server Version:
  • Deployment Method:
  • Multi Node? Number of Running Nodes:
  • Client Language and Version:
  • Multitenancy?:

Any additional Information

2

hi @Tejas_Sharma !!

Were you able to fix this? I was out today, but now I got info about an outage in europe-west3 regarding GRPC.

So they are probably related.

Let me know if this is fixed now.

Thanks!

3

Hi @DudaNogueira I’m still getting this and it was before this europe outage happened (we are us-west).

I’m also confused regarding the documentation above because it says it automatically uses GRPC underneath the hood anyways without me specifying anything on Python v4?

(Oh and for some reason, I had posted this but when I came back to check it was still in my drafts, so sorry for late response)

4

hi @Tejas_Sharma !!

That’s right.

Some method of the client are still using the REST endpoints, but we are moving towards only using GRPC, so we are slowly migrating those methods from REST to GRPC.

But note that this is “under the hood”, so it shouldn’t affect the client syntax.

So now, in python v4, when you instantiate the python client, it will first check both REST and GRPC endpoints, and use it accordingly.

Let me know if that helps.

5

Thanks @DudaNogueira ! Good to know

1 Like