The Wayback Machine - https://web.archive.org/web/20220328134510/https://github.com/topics/service-discovery
Skip to content
#

service-discovery

Here are 573 public repositories matching this topic...

consul
FFMMM
FFMMM commented Mar 3, 2022

Overview

I think it's time to start iterating on hashicorp/consul#11536 . Since, I've gathered some feedback from folks that we can implement.

Suggestions

Let's look at an errored check:

PR seems to modify metrics behavior. It seems no tests or test behavior has been modified.
Please update the PR with any relevant updated testing or add a pr/no-m
good first issue theme/github-management
xiaowenyu
xiaowenyu commented Mar 1, 2022

组件:
spring-cloud-starter-stream-rocketmq
问题版本:
2.2.7.RELEASE; 2021.0.1.0

问题详情:
stream-rocketmq 2.2.6.RELEASE 升级到 2.2.7.RELEASE 后,无法正常conmit offset

重现步骤:
1.运行的demo如下,使用 AcknowledgmentCallback.noAutoAck() 关闭自动ack,打印之后再 ack

 @Bean
    public ApplicationRunner poller(PollableMessageSource dest1In) {
        return args -> {
            while (true) {
                if (!dest1In.
fyodor
fyodor commented Mar 16, 2021

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

express-gateway
XVincentX
XVincentX commented Jan 2, 2018

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

shichaoyuan
shichaoyuan commented Mar 17, 2022

目前在代码里有两次计算 ServiceInstanceRevision 的方法:

  1. 消费 comRevisionCh 异步计算
  2. ServiceInstancesCache 发现流程中同步补偿计算
    这两个地方使用的 service 信息不一致,前者是 revision,后者是 id
// processRevisionWorker 处理revision计算的函数
func (nc *NamingCache) processRevisionWorker(req *revisionNotify) bool {
	if req == nil {
		log.CacheScope().Errorf("[Cache][Revision] get null revision request")
		return false
	}

	if req.servi
bug good first issue
akaxb
akaxb commented Dec 10, 2020

Describe the bug

A clear and concise description of the bug.
when my asp.net core 3.1 app host in IIS, the url console is 127.0.0.1,so,when i have Multiple instances,the instances name will be the same,such as 127.0.0.1:svaname:port,eureka server think they are a single instance.
i print the console in source code:
![image](https://user-images.githubusercontent.com/6300834/101754289-8ad92

Type/bug help wanted good first issue Component/Discovery
sample-spring-microservices-new

Demo for Spring Boot 2 and Spring Cloud microservices with distributed configuration (Spring Cloud Config), service discovery (Eureka), API gateway (Spring Cloud Gateway, Zuul), Swagger2 API documentation, logs correlation using Spring Cloud Sleuth and many more

  • Updated Feb 13, 2022
  • Java

a microservices library - scalecube-services is a high throughput, low latency reactive microservices library built to scale. it features: API-Gateways, service-discovery, service-load-balancing, the architecture supports plug-and-play service communication modules and features. built to provide performance and low-latency real-time stream-processing. its open and designed to accommodate changes. (no sidecar in a form of broker or any kind)

  • Updated Mar 6, 2022
  • Java

Improve this page

Add a description, image, and links to the service-discovery topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the service-discovery topic, visit your repo's landing page and select "manage topics."

Learn more