few-rainbow-57094
06/29/2022, 7:35 PMcreamy-van-28626
06/30/2022, 6:41 AMpowerful-oyster-96008
06/30/2022, 3:54 PMbitter-lamp-84598
06/30/2022, 4:44 PMjolly-afternoon-92582
06/30/2022, 4:45 PMpurple-tailor-57675
06/30/2022, 6:15 PMfew-rainbow-57094
06/30/2022, 8:41 PMdatahub docker quickstart
everything runs fine, but if I instead run docker-compose up -d
with the attached file my ui becomes all wonky and unsuable. Has anypne ever experienced this?colossal-needle-73093
07/02/2022, 10:06 AMProcess 'command 'xx/datahub/datahub-web-react/.gradle/yarn/yarn-v1.22.0/bin/yarn'' finished with non-zero exit value 1
colossal-needle-73093
07/02/2022, 2:33 PMExecution failed for task ':datahub-frontend:compileScala'.
> Compilation failed
2. After I install scala manually, it apprears the following info:
[Error] /datahub/datahub-frontend/build/src/play/routes/router/Routes.scala:23: type CentralLogoutController is not a member of package controllers
[Error] /datahub/datahub-frontend/build/src/play/routes/router/Routes.scala:27: type TrackingController is not a member of package controllers
[Error] /datahub/datahub-frontend/build/src/play/routes/router/Routes.scala:40: type CentralLogoutController is not a member of package controllers
[Error] /datahub/datahub-frontend/build/src/play/routes/router/Routes.scala:44: type TrackingController is not a member of package controllers
gray-architect-29447
07/04/2022, 1:05 AMmany-hairdresser-62442
07/04/2022, 10:49 AMsteep-pizza-13640
07/04/2022, 2:42 PMhelpful-processor-71693
07/06/2022, 8:17 AMrapid-book-98432
07/06/2022, 11:52 AMrapid-book-98432
07/06/2022, 12:41 PMfew-grass-66826
07/06/2022, 10:49 PMfresh-memory-20741
07/07/2022, 3:19 AMfresh-memory-20741
07/07/2022, 3:20 AMrich-salesmen-55640
07/07/2022, 10:03 AMsilly-ice-4153
07/07/2022, 10:31 AMcreamy-van-28626
07/07/2022, 11:43 AMfancy-artist-67223
07/07/2022, 1:49 PMcalm-dinner-63735
07/07/2022, 8:39 PMfaint-translator-23365
07/07/2022, 9:36 PMcreamy-van-28626
07/11/2022, 11:08 AMfew-grass-66826
07/11/2022, 11:10 PMrich-policeman-92383
07/12/2022, 8:23 AMCaused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dataHubAuthorizerFactory': Unsatisfied dependency expressed through field 'entityClient'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'javaEntityClientFactory': Unsatisfied dependency expressed through field '_entityService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'entityAspectDao' defined in com.linkedin.gms.factory.entity.EntityAspectDaoFactory: Unsatisfied dependency expressed through method 'createEbeanInstance' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ebeanServer' defined in com.linkedin.gms.factory.entity.EbeanServerFactory: 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)
Datahub Upgrade Error:
022-07-12 07:56:35.388 INFO 1 --- [ main] ConditionEvaluationReportLoggingListener :
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2022-07-12 07:56:35.595 ERROR 1 --- [ main] o.s.boot.SpringApplication : Application run failed
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
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
pods status: Prerequisites are running fine
NAME READY STATUS RESTARTS AGE
datahub-acryl-datahub-actions-6598bff46-mdlcw 1/1 Running 6 (4m59s ago) 31m
datahub-datahub-frontend-7dbbd4644f-hqnfx 1/1 Running 0 31m
datahub-datahub-gms-996bbbfc9-2pgf7 0/1 Running 5 (4m18s ago) 31m
datahub-datahub-upgrade-job-b9jlz 0/1 Error 0 28m
datahub-datahub-upgrade-job-dp2qb 0/1 Error 0 30m
datahub-datahub-upgrade-job-dr7p8 0/1 Error 0 29m
datahub-datahub-upgrade-job-gb9w7 0/1 Error 0 27m
datahub-datahub-upgrade-job-mxnh2 0/1 Error 0 24m
datahub-datahub-upgrade-job-r4lv6 0/1 Error 0 31m
datahub-datahub-upgrade-job-z7r9x 0/1 Error 0 30m
datahub-elasticsearch-setup-job-pjtpm 0/1 Completed 0 34m
datahub-kafka-setup-job-c99cc 0/1 Completed 0 34m
datahub-mysql-setup-job-nckpd 0/1 Completed 0 32m
prerequisites-cp-schema-registry-555899678b-xxt69 1/1 Running 0 4m38s
prerequisites-kafka-0 1/1 Running 0 39m
prerequisites-mysql-0 1/1 Running 0 4m34s
prerequisites-zookeeper-0 1/1 Running 0 4m34s
enough-afternoon-42060
07/13/2022, 6:30 AMfaint-translator-23365
07/13/2022, 10:33 AMmicroscopic-mechanic-13766
07/13/2022, 12:58 PMELASTICSEARCH_HOST
in the Docker-compose you can indicate the host of one of the masters of ES. A normal ES deployment has more than 1 master so that, in case it falls, the tool is still operative.
The problem is that, as in Datahub you can only specify only one master, if that master falls, DataHub users won't be able to do anything until that node recovers from failing.
Is there a way to specify 2 hosts of ES so that this problem is solved??
Thanks in advance!