Created 08-27-2018 06:08 AM
my error logs below
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Aug 27, 2018 1:06:46 PM com.google.inject.assistedinject.FactoryProvider2 isValidForOptimizedAssistedInject WARNING: AssistedInject factory org.apache.ambari.server.state.cluster.ClusterFactory will be slow because class org.apache.ambari.server.state.cluster.ClusterImpl has assisted Provider dependencies or injects the Injector. Stop injecting @Assisted Provider<T> (instead use @Assisted T) or Injector to speed things up. (It will be a ~6500% speed bump!) The exact offending deps are: [Key[type=com.google.inject.Injector, annotation=[none]]@org.apache.ambari.server.state.cluster.ClusterImpl.<init>()[1]] Aug 27, 2018 1:06:46 PM com.google.inject.assistedinject.FactoryProvider2 isValidForOptimizedAssistedInject WARNING: AssistedInject factory org.apache.ambari.server.controller.ResourceProviderFactory will be slow because class org.apache.ambari.server.controller.internal.HostComponentResourceProvider has assisted Provider dependencies or injects the Injector. Stop injecting @Assisted Provider<T> (instead use @Assisted T) or Injector to speed things up. (It will be a ~6500% speed bump!) The exact offending deps are: [Key[type=com.google.inject.Injector, annotation=[none]]@org.apache.ambari.server.controller.internal.HostComponentResourceProvider.<init>()[1]] Aug 27, 2018 1:06:46 PM com.google.inject.assistedinject.FactoryProvider2 isValidForOptimizedAssistedInject WARNING: AssistedInject factory org.apache.ambari.server.state.scheduler.RequestExecutionFactory will be slow because class org.apache.ambari.server.state.scheduler.RequestExecutionImpl has assisted Provider dependencies or injects the Injector. Stop injecting @Assisted Provider<T> (instead use @Assisted T) or Injector to speed things up. (It will be a ~6500% speed bump!) The exact offending deps are: [Key[type=com.google.inject.Injector, annotation=[none]]@org.apache.ambari.server.state.scheduler.RequestExecutionImpl.<init>()[2]] Aug 27, 2018 1:06:46 PM com.google.inject.assistedinject.FactoryProvider2 isValidForOptimizedAssistedInject WARNING: AssistedInject factory org.apache.ambari.server.state.scheduler.RequestExecutionFactory will be slow because class org.apache.ambari.server.state.scheduler.RequestExecutionImpl has assisted Provider dependencies or injects the Injector. Stop injecting @Assisted Provider<T> (instead use @Assisted T) or Injector to speed things up. (It will be a ~6500% speed bump!) The exact offending deps are: [Key[type=com.google.inject.Injector, annotation=[none]]@org.apache.ambari.server.state.scheduler.RequestExecutionImpl.<init>()[3]] Aug 27, 2018 1:06:49 PM com.google.inject.internal.ProxyFactory <init> WARNING: Method [public void org.apache.ambari.server.orm.dao.RepositoryVersionDAO.create(java.lang.Object)] is synthetic and is being intercepted by [org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor@295bf2a]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. Aug 27, 2018 1:06:49 PM com.google.inject.internal.ProxyFactory <init> WARNING: Method [public void org.apache.ambari.server.orm.dao.HostVersionDAO.create(java.lang.Object)] is synthetic and is being intercepted by [org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor@295bf2a]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. Aug 27, 2018 1:06:50 PM com.google.inject.internal.ProxyFactory <init> WARNING: Method [public void org.apache.ambari.server.orm.dao.AmbariConfigurationDAO.create(java.lang.Object)] is synthetic and is being intercepted by [org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor@295bf2a]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. Aug 27, 2018 1:06:50 PM com.google.inject.internal.ProxyFactory <init> WARNING: Method [public java.lang.Object org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call() throws java.lang.Exception] is synthetic and is being intercepted by [org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor@265bd546]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. An unexpected error occured during starting Ambari Server. org.apache.ambari.server.AmbariException: Current database store version is not compatible with current server version, serverVersion=2.7.0.0, schemaVersion=2.1.2 at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkDBVersionCompatible(DatabaseConsistencyCheckHelper.java:236) at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1096)
=================================================================
After i upgrade ambari-server it doesn't work...
What's the problem?
Created 08-27-2018 06:10 AM
The following error indicates that your Ambari Database schema version is 2.1.2 and you have installed Ambari Binary verison 2.7
Current database store version is not compatible with current server version, serverVersion=2.7.0.0, schemaVersion=2.1.2 at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkDBVersionCompatible(DatabaseConsistencyCheckHelper.java:236) at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1096)
.
You can not upgrade your ambari directly from Ambari 2.1.2 to Ambari 2.7
So please make sure to upgrade your ambari to 2.5 and then from 2.5 to 2.6 first and then you should be able to upgrade it from Ambari 2.6 to Ambari 2.7
Please refer to the following doc for more details: https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_gu...
NOTE: from above link.
Ambari 2.7 only supports fully managing a HDP 3.0 cluster. If you are running any other HDP version, you must first upgrade to HDP 2.6 using Ambari 2.6, then upgrade to Ambari 2.7 and use it to upgrade your cluster to HDP 3.0.
.
Created 08-27-2018 06:10 AM
The following error indicates that your Ambari Database schema version is 2.1.2 and you have installed Ambari Binary verison 2.7
Current database store version is not compatible with current server version, serverVersion=2.7.0.0, schemaVersion=2.1.2 at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkDBVersionCompatible(DatabaseConsistencyCheckHelper.java:236) at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1096)
.
You can not upgrade your ambari directly from Ambari 2.1.2 to Ambari 2.7
So please make sure to upgrade your ambari to 2.5 and then from 2.5 to 2.6 first and then you should be able to upgrade it from Ambari 2.6 to Ambari 2.7
Please refer to the following doc for more details: https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_gu...
NOTE: from above link.
Ambari 2.7 only supports fully managing a HDP 3.0 cluster. If you are running any other HDP version, you must first upgrade to HDP 2.6 using Ambari 2.6, then upgrade to Ambari 2.7 and use it to upgrade your cluster to HDP 3.0.
.
Created 08-27-2018 06:14 AM
You can find more detailed Ambari Upgrade Path here:
Ambari 2.1.2 to Ambari 2.5
Then Ambari 2.5 to Ambari 2.6
and then From ambari 2.6 to Ambari 2.7
Created 08-27-2018 08:42 AM
Thank you!!
I solved the problem.