https://datahubproject.io logo
#troubleshoot
Title
# troubleshoot
n

nutritious-bird-77396

06/09/2022, 6:58 PM
Error when trying to run
datahub-upgrade
After setting all the envs in local as in here - https://github.com/datahub-project/datahub/blob/master/docker/datahub-upgrade/env/docker-without-neo4j.env and successfully building
./gradlew :datahub-upgrade:build
executing
java -jar datahub-upgrade/build/libs/datahub-upgrade.jar -u RestoreIndices
throws Errors. Details of the Error in 🧵 Any help on this would be great!
plus1 1
Copy code
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'upgradeCli': Unsatisfied dependency expressed through field 'noCodeUpgrade'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ebeanServer' defined in class path resource [com/linkedin/gms/factory/entity/EbeanServerFactory.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.ebean.EbeanServer]: Factory method 'createServer' threw exception; nested exception is java.lang.NullPointerException
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:659) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.20.jar!/:5.3.20]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.20.jar!/:5.3.20]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) ~[spring-boot-2.5.12.jar!/:2.5.12]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:448) ~[spring-boot-2.5.12.jar!/:2.5.12]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:339) ~[spring-boot-2.5.12.jar!/:2.5.12]
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:143) [spring-boot-2.5.12.jar!/:2.5.12]
	at com.linkedin.datahub.upgrade.UpgradeCliApplication.main(UpgradeCliApplication.java:19) [classes!/:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_292]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_292]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_292]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_292]
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) [datahub-upgrade.jar:na]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:108) [datahub-upgrade.jar:na]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) [datahub-upgrade.jar:na]
	at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88) [datahub-upgrade.jar:na]
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ebeanServer' defined in class path resource [com/linkedin/gms/factory/entity/EbeanServerFactory.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.ebean.EbeanServer]: Factory method 'createServer' threw exception; nested exception is java.lang.NullPointerException
	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:658) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:486) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1352) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1195) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1389) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1309) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:656) ~[spring-beans-5.3.20.jar!/:5.3.20]
	... 26 common frames omitted
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.ebean.EbeanServer]: Factory method 'createServer' threw exception; nested exception is java.lang.NullPointerException
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185) ~[spring-beans-5.3.20.jar!/:5.3.20]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:653) ~[spring-beans-5.3.20.jar!/:5.3.20]
	... 41 common frames omitted
Caused by: java.lang.NullPointerException: null
	at io.ebean.datasource.pool.ConnectionPool.notifyDataSourceIsDown(ConnectionPool.java:406) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.ConnectionPool.createUnpooledConnection(ConnectionPool.java:535) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.ConnectionPool.createUnpooledConnection(ConnectionPool.java:524) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.ConnectionPool.createConnectionForQueue(ConnectionPool.java:766) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.PooledConnectionQueue.ensureMinimumConnections(PooledConnectionQueue.java:227) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.ConnectionPool.initialise(ConnectionPool.java:301) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.pool.ConnectionPool.<init>(ConnectionPool.java:246) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebean.datasource.core.Factory.createPool(Factory.java:15) ~[ebean-datasource-4.3.3.jar!/:na]
	at io.ebeaninternal.server.core.DefaultContainer.getDataSourceFromConfig(DefaultContainer.java:273) ~[ebean-11.33.3.jar!/:na]
	at io.ebeaninternal.server.core.DefaultContainer.setDataSource(DefaultContainer.java:217) ~[ebean-11.33.3.jar!/:na]
	at io.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:103) ~[ebean-11.33.3.jar!/:na]
	at io.ebeaninternal.server.core.DefaultContainer.createServer(DefaultContainer.java:35) ~[ebean-11.33.3.jar!/:na]
	at io.ebean.EbeanServerFactory.createInternal(EbeanServerFactory.java:109) ~[ebean-11.33.3.jar!/:na]
	at io.ebean.EbeanServerFactory.create(EbeanServerFactory.java:70) ~[ebean-11.33.3.jar!/:na]
	at com.linkedin.gms.factory.entity.EbeanServerFactory.createServer(EbeanServerFactory.java:33) ~[factories.jar!/:na]
	at com.linkedin.gms.factory.entity.EbeanServerFactory$$EnhancerBySpringCGLIB$$a0cc7a78.CGLIB$createServer$0(<generated>) ~[factories.jar!/:na]
	at com.linkedin.gms.factory.entity.EbeanServerFactory$$EnhancerBySpringCGLIB$$a0cc7a78$$FastClassBySpringCGLIB$$2d92a0be.invoke(<generated>) ~[factories.jar!/:na]
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244) ~[spring-core-5.3.20.jar!/:5.3.20]
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331) ~[spring-context-5.3.20.jar!/:5.3.20]
	at com.linkedin.gms.factory.entity.EbeanServerFactory$$EnhancerBySpringCGLIB$$a0cc7a78.createServer(<generated>) ~[factories.jar!/:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_292]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_292]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_292]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_292]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) ~[spring-beans-5.3.20.jar!/:5.3.20]
	... 42 common frames omitted
I am guessing if the error could be because of I set
EBEAN_DATASOURCE_DRIVER
as
org.postgresql.Driver
As this driver is not found in the classpath it might throw the error...not sure still figuring it out....
l

lemon-hydrogen-83671

06/09/2022, 8:36 PM
yeah im in the same boat here 😛
but it does look like it is in the classpath so not sure, i thnk we are just missing a environment variable or something
n

nutritious-bird-77396

06/09/2022, 9:20 PM
yeah its in the dependencies https://github.com/datahub-project/datahub/blob/master/datahub-upgrade/build.gradle#L28 and i confirmed by extracting the jar too -
Copy code
extracted: BOOT-INF/lib/postgresql-42.3.3.jar
Even a debug doesn't provide any more info.
Here are some of my env vars..
Copy code
export EBEAN_DATASOURCE_HOST=<hostname>:5432
export EBEAN_DATASOURCE_URL=jdbc:postgresql://<data-source-url>:5432/datahub
export KAFKA_BOOTSTRAP_SERVER=<kafka-bootstrap>
export KAFKA_SCHEMAREGISTRY_URL=https://<schema-registry>
export ELASTICSEARCH_HOST=<elastic-host>
export ELASTICSEARCH_PORT=443
export ELASTICSEARCH_USE_SSL=true
export USE_AWS_ELASTICSEARCH=true
export GRAPH_SERVICE_IMPL="elasticsearch"
export DATAHUB_GMS_HOST="datahub-gms.<domain>.com"
export DATAHUB_GMS_PORT="8080"
export ENTITY_REGISTRY_CONFIG_PATH=/datahub/datahub-gms/resources/entity-registry.yml
export SPRING_KAFKA_PROPERTIES_SECURITY_PROTOCOL=SASL_SSL
export SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_LOCATION=/usr/lib/jvm/java-1.8-openjdk/jre/lib/security/cacerts
export SPRING_KAFKA_PROPERTIES_SASL_MECHANISM=SCRAM-SHA-512
export MSK_USERNAME=<username>
export MSK_PASSWORD=<password>
export SPRING_KAFKA_PROPERTIES_SASL_JAAS_CONFIG="org.apache.kafka.common.security.scram.ScramLoginModule required username="${MSK_USERNAME}" password="${MSK_PASSWORD}";"
export JAVA_OPTS="-Xms1g -Xmx1g"
export EBEAN_DATASOURCE_USERNAME=<data-source-user-name>
export EBEAN_DATASOURCE_PASSWORD=<data-source-password>
export EBEAN_DATASOURCE_DRIVER="org.postgresql.Driver"
I am using RDS Postgres, AWS Open Search and MSK (connect using SASL) ^^^
@early-lamp-41924 Do you see if we are missing any env var?
l

lemon-hydrogen-83671

06/09/2022, 11:14 PM
we run our own postgres/kafka/etc. i have these set
Copy code
DATAHUB_GMS_HOST
DATAHUB_GMS_PORT
EBEAN_DATASOURCE_DRIVER
EBEAN_DATASOURCE_HOST
EBEAN_DATASOURCE_PASSWORD
EBEAN_DATASOURCE_URL
EBEAN_DATASOURCE_USERNAME
ELASTICSEARCH_HOST
ELASTICSEARCH_PASSWORD
ELASTICSEARCH_PORT
ELASTICSEARCH_SSL_KEY_PASSWORD
ELASTICSEARCH_SSL_KEYSTORE_FILE
ELASTICSEARCH_SSL_KEYSTORE_PASSWORD
ELASTICSEARCH_SSL_KEYSTORE_TYPE
ELASTICSEARCH_SSL_TRUSTSTORE_FILE
ELASTICSEARCH_SSL_TRUSTSTORE_PASSWORD
ELASTICSEARCH_SSL_TRUSTSTORE_TYPE
ELASTICSEARCH_USE_SSL
ELASTICSEARCH_USERNAME
GRAPH_SERVICE_IMPL
KAFKA_BOOTSTRAP_SERVER
KAFKA_SCHEMA_REGISTRY_SECURITY_PROTOCOL
KAFKA_SCHEMA_REGISTRY_SSL_KEYSTORE_LOCATION
KAFKA_SCHEMA_REGISTRY_SSL_KEYSTORE_PASSWORD
KAFKA_SCHEMA_REGISTRY_SSL_TRUSTSTORE_LOCATION
KAFKA_SCHEMA_REGISTRY_SSL_TRUSTSTORE_PASSWORD
KAFKA_SCHEMAREGISTRY_URL
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SECURITY_PROTOCOL
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SSL_KEY_PASSWORD
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SSL_KEYSTORE_LOCATION
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SSL_KEYSTORE_PASSWORD
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SSL_TRUSTSTORE_LOCATION
SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_SSL_TRUSTSTORE_PASSWORD
SPRING_KAFKA_PROPERTIES_SECURITY_PROTOCOL
SPRING_KAFKA_PROPERTIES_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM
SPRING_KAFKA_PROPERTIES_SSL_KEY_PASSWORD
SPRING_KAFKA_PROPERTIES_SSL_KEYSTORE_LOCATION
SPRING_KAFKA_PROPERTIES_SSL_KEYSTORE_PASSWORD
SPRING_KAFKA_PROPERTIES_SSL_PROTOCOL
SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_LOCATION
SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_PASSWORD
it might not even be a missing variable, that was just my best guess from the error message.
e

early-lamp-41924

06/10/2022, 12:40 AM
Hmn yeah as you mentioned. this is when it fails to connect to ebeans for some reason. Can you compare all envs starting with EBEANS to the ones for gms?
Assuming your GMS deploy has no issues
l

lemon-hydrogen-83671

06/10/2022, 5:25 AM
Thanks! Yeah turns out that the postgres host i was trying to reach was not accessible from local lol @nutritious-bird-77396 make sure you can actually hit your postgres url from wherever you are running the upgrade app!
n

nutritious-bird-77396

06/10/2022, 5:10 PM
Turns out that's exactly the issue I was facing too. Forgot that we were using StrongDM so have to use the localhost for the database hostnames. Once that is fixed the app worked. Thanks to both of you guys.
e

early-lamp-41924

06/10/2022, 5:11 PM
Power of the community!! Glad it’s all working now!
thank you 1
l

lemon-hydrogen-83671

06/10/2022, 6:13 PM
🥳 Any idea how we can get a more detailed log? Usually if we are missing a bean or if theres a connection issue i would expect something more descriptive then a null pointer error
1
Not a big deal but it was quite a goose chase
n

nutritious-bird-77396

06/10/2022, 6:59 PM
I was letting it run on the environment for a while after more than hour with lot more records sent to GMS i see the below message.
Copy code
Reading rows 2367000 through 2368000 from the aspects table.
Caught exception during attempt 0 of Step with id SendMAEStep: java.lang.IllegalStateException: Aspect clientId could not be found
Retrying 0 more times...
Failed Step 3/3: SendMAEStep. Failed after 0 retries.
Exiting upgrade RestoreIndices with failure.
Upgrade RestoreIndices completed with result FAILED. Exiting...
I think
clientId
was added in a later version. Is there a way to get past this? Do i need to do any upgrade?
Looks like the error is from here - https://github.com/datahub-project/datahub/blob/master/metadata-io/src/main/java/com/linkedin/metadata/entity/EntityUtils.java#L57 Need to dig thru to find the right record with the issue...
clientId
aspect is added as part of the Datahub Telemetry - https://datahubproject.io/docs/generated/metamodel/entities/telemetry/#telemetryclientid It has enabled by default since
v0.8.35
- https://datahubproject.io/docs/releases#full-commit-log-1
e

early-lamp-41924

06/10/2022, 7:59 PM
@orange-night-91387 another case of this happening
One easy way is to delete the row with clientId as it is not valid
nod 1
1
@orange-night-91387 we need a way to automatically detect this bad row and delete it on start up
n

nutritious-bird-77396

06/10/2022, 8:01 PM
Got it. Just to understand the history is this an aspectName change from one version to the other?
@orange-night-91387 ^^
o

orange-night-91387

06/10/2022, 8:08 PM
There was a typo in the name that actually got inserted into the DB when updating from review comments
I can add a hook to delete the aspect, but that will still require people to update to latest (where there is no error anyway). Might be easier to make a note that you can either: 1. Hard delete the entity and restart GMS 2. Manually delete the
clientId
aspect row from the DB
Hard deleting the entity will mess up our stats temporarily though
For the history you can check out
DailyReport.java
n

nutritious-bird-77396

06/10/2022, 8:16 PM
I can definitely delete it but it might still impact others in the future. May be checking if the
clientId
aspect for the urn exists and removing might make it future proof.
Also i don't have write access to prod (which makes sense) so i will have to delete the entity and restart to remove the aspect as
datahub-cli
doesn't provide a feature to delete aspects yet.
nod 1
o

orange-night-91387

06/10/2022, 8:29 PM
DataHub Upgrade with the latest version won't hit this error, so adding a code fix for it won't solve the problem for people hitting this on release 0.8.35/36 who can't upgrade immediately. I definitely agree with adding a hook to at least remove the unnecessary aspect for future releases for not causing issues in other unexpected ways. It won't fix this specific problem though
e

early-lamp-41924

06/10/2022, 8:31 PM
We could create a hook that blindly deletes all rows with an aspectName that is deprecated
nod 1
I think it’s necessary considering that this breaks anyone who deployed this specific release version
o

orange-night-91387

06/10/2022, 8:32 PM
Yeah, basically run through and if it doesn't exist in EntityRegistry delete it
plus1 2
n

nutritious-bird-77396

06/10/2022, 8:32 PM
Just to let you know even i couldn't delete from the cli as well as it goes thru API which throws error when its a unknown aspect.
Copy code
OperationalError: ('Unable to emit metadata to DataHub GMS', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status:500]: java.lang.RuntimeException: Unknown aspect status for entity telemetry\n\tat com.linkedin.metadata.restli.RestliUtil.toTask(Restl
@orange-night-91387 Are you saying this is fixed in 0.8.38?
e

early-lamp-41924

06/10/2022, 8:33 PM
Let’s get this out as soon as possible, as upgrading won’t help
👍 1
o

orange-night-91387

06/10/2022, 8:37 PM
I'll see if I can get it out today, I don't think it should be too complicated
@nutritious-bird-77396 That's saying it doesn't have a Status, try doing a hard delete
DataHub upgrade should pass by the issue in latest and only fail that single record
n

nutritious-bird-77396

06/10/2022, 8:45 PM
@orange-night-91387 No luck...
Copy code
datahub@datahub-cli:/$ datahub delete --urn "urn:li:telemetry:clientId" --hard
Took 2.335 seconds to hard delete 0 rows for 1 entities
The urn and aspect still exists as well
😞 1
o

orange-night-91387

06/13/2022, 3:09 PM
https://github.com/datahub-project/datahub/pull/5148/files put up this PR on Friday, fixes it from two directions by adding an upgrade option to clear it out and adding a bootstrap step that will delete it out
n

nutritious-bird-77396

06/13/2022, 4:38 PM
This is great Ryan, this might be a good generic solution. I was also thinking about a direct fix to the init scripts to remove the wrong aspect entry - https://github.com/datahub-project/datahub/blob/master/docker/postgres/init.sql
o

orange-night-91387

06/13/2022, 4:43 PM
I don't think we would want it at low a level, that script generally gets run once and we would have to put it in all of the scripts for all backends we support.
plus1 1
It also would effectively be the same as providing a one-off SQL statement to run
n

nutritious-bird-77396

06/14/2022, 4:07 PM
Awesome! looking forward for this fix in
0.8.39
. Thanks Ryan.
c

colossal-easter-99672

06/29/2022, 1:59 PM
Hello, team. Is there any fix for this error? I delete this string in db, but it appears in db again. Error on restoring search and graph indices
Copy code
Reading rows 103000 through 104000 from the aspects table.
Caught exception during attempt 0 of Step with id SendMAEStep: java.lang.IllegalStateException: Aspect clientId could not be found
Retrying 0 more times...
Failed Step 3/3: SendMAEStep. Failed after 0 retries.
Exiting upgrade RestoreIndices with failure.
Upgrade RestoreIndices completed with result FAILED. Exiting...
o

orange-night-91387

06/29/2022, 2:58 PM
Hi! This should be fixed in the latest release. If you're able to upgrade I would recommend taking that path. If you are unable to upgrade, it will repopulate on GMS restart. We added a job to the datahub-upgrade image to remove it as well and the latest datahub-upgrade will not fail if it is present, so if you can't upgrade your whole stack please try running the restore indices with an upgraded datahub-upgrade.
thank you 1
6 Views