我正在尝试设置一个带有涡轮机的hystrix仪表板。我没有使用尤里卡,而是想使用FileBasedInstanceDiscovery。我正在尝试对此进行配置,但遵循在线文档似乎不起作用。它总是尝试使用Eureka发现客户端。我尝试从我的pom中排除eureka,但随后它又返回到另一个发现客户端CommonsInstanceDiscovery。
这是我的application.properties:
turbine.aggregator.clusterConf=mycluster
turbine.instanceUrlSuffix.mycluster=8080/hystrix.stream
turbine.FileBasedInstanceDiscovery.filePath=turbine.hostnames.txt
turbine.InstanceMonitor.eventStream.skipLineLogic.enabled=false
InstanceDiscovery.impl=com.netflix.turbine.discovery.FileBasedInstanceDiscovery有没有其他方法可以做到这一点?另外,对于我的涡轮机主机名的filePath,它从哪里开始查找?我可以把这个文件放在jar的resources目录下吗?
下面是我的pom文件依赖关系:
<properties>
<java.version>1.8</java.version>
<spring-cloud.version>Greenwich.SR1</spring-cloud.version>
</properties>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web-services</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-netflix-hystrix-dashboard</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-netflix-turbine</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-netflix-eureka-client</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>${spring-cloud.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>发布于 2019-05-15 21:44:58
有些文档对涡轮机不清楚且相互冲突,我认为这是因为有spring-cloud-netflix项目和一个独立的涡轮机项目。无论如何,如果你正在构建一个spring-boot应用程序,那么这个属性是没有用的:
InstanceDiscovery.impl=com.netflix.turbine.discovery.FileBasedInstanceDiscovery如果你想改变InstanceDiscovery的实现很简单,只需创建一个像这样实现InstanceDiscovery的bean:
@Bean
public InstanceDiscovery instanceDiscovery() {
//choose either one of the provided implementations from spring or
//create your own
return new ConfigPropertyBasedDiscovery();
//return new FileBasedInstanceDiscovery();
}确保将其放在@Configuration类中。我的代码最初只在我的SpringBootApplication类中,但这不允许您覆盖默认的实现。
发布于 2020-03-30 15:51:56
我使用过ConfigPropertyBasedDiscovery,但我遇到了下面的异常情况
2020-03-30 13:19:14.360 INFO 17060 --- [ Timer-0] c.n.t.discovery.InstanceObservable : Hosts up:1, hosts down: 017060 -03-30 13:19:14.371错误2020- Timer-0 c.n.t.monitor.cluster.ClusterMonitor :无法在hostUp上启动监视器: StatsInstance hostname=localhost:8080,StatsInstance: VIBuilder,isUp: true,attrs={}
java.lang.RuntimeException:配置为使用端口,但是com.netflix.turbine.monitor.instance.InstanceMonitor.(InstanceMonitor.java:185) ~ org.springframework.cloud.netflix.turbine.SpringClusterMonitor$1.getUrlPath(SpringClusterMonitor.java:114) ~spring-cloud-netflix-turbine-2.2.2.RELEASE.jar:2.2.2.RELEASE -core-1.0.0.jar:na的com.netflix.turbine.monitor.instance.InstanceMonitor.(InstanceMonitor.java:173) ~turbine securePort -1处的端口或核心不在主机属性中。0.0.jar:na at com.netflix.turbine.monitor.cluster.ClusterMonitor$ClusterMonitorInstanceManager.getMonitor(ClusterMonitor.java:300) ~turbine core-1.0.0.jar:na at com.netflix.turbine.monitor.cluster.ClusterMonitor$ClusterMonitorInstanceManager.hostUp(ClusterMonitor.java:268) ~turbine core-1.0.0.jar:na at com.netflix.turbine.monitor.cluster.ClusterMonitor$ClusterMonitorInstanceManager.hostsUp(ClusterMonitor.java:312) ~turbine core-1.0.0.jar:na at com。netflix.turbine.discovery.InstanceObservable$1.run(InstanceObservable.java:298) ~ java.base/java.util.TimerThread.mainLoop(Timer.java:556) -core-1.0.0.jar:na at java.base/java.util.TimerThread.run(Timer.java:506) ~na:na at java.base/java.util.TimerThread.run(Timer.java:506) ~na:na
https://stackoverflow.com/questions/56136876
复制相似问题