Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide an option for setting discovery to false #3155

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Provide an option for setting discovery to false #3155

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
bug Something isn't working major Server Tools

Comments

@monetdb-team
Copy link

Date: 2012-10-09 12:31:21 +0200
From: Ashish Kumar Singh <>
To: Merovingian devs <>
Version: 11.13.3 (Oct2012)
CC: ashishk

Last updated: 2012-11-21 14:49:40 +0100

Comment 17764

Date: 2012-10-09 12:31:21 +0200
From: Ashish Kumar Singh <>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4
Build Identifier:

As of now there is no way we can switch of UDP discovery mode to be disabled. Though it is a very good feature but may not be acceptable in certain situations

Reproducible: Always

Steps to Reproduce:

1.Set Discovery to false using monetdbd
2.Try to start server
3.Server startup fails with a message uanble to check status.

Actual Results:

server startup fails

Expected Results:

Server start up should succeed with Discovery disabled.

Comment 17765

Date: 2012-10-09 12:54:01 +0200
From: @grobian

This is indeed a stupid logic error.

Comment 17766

Date: 2012-10-09 12:58:20 +0200
From: @grobian

Changeset 4450ff9fa3f2 made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4450ff9fa3f2

Changeset description:

merovingian: fix logic error for discovery

We shouldn't treat discovery being disabled as failure, but just
optionally skip setting up the UDP channel.  Fixes bug #3155.

Comment 17767

Date: 2012-10-09 12:59:42 +0200
From: @grobian

Fixed

Comment 17769

Date: 2012-10-09 14:02:45 +0200
From: Ashish Kumar Singh <>

when next stable build with this fix is scheduled? any hints on exact date will be helpful!

Thanks!

Comment 17772

Date: 2012-10-09 14:04:53 +0200
From: @grobian

It's being built right now, so, I hope today or tomorrow to release the release candidate. If that one behaves well, we can release it next week. Any testing would be appreciated.

Comment 17811

Date: 2012-10-14 11:13:52 +0200
From: Ashish Kumar Singh <>

HI,

When is release candidate going to be out? Is it on track?

Regards,
Ashish

Comment 17813

Date: 2012-10-15 08:30:50 +0200
From: @grobian

(In reply to comment 6)

When is release candidate going to be out? Is it on track?

not really, there hasn't been much feedback yet, and a fix was made for an issue that might warrant a rebuild

I think we'll evaluate tomorrow.

Comment 17814

Date: 2012-10-15 08:32:23 +0200
From: @grobian

in case you're looking for the candidate itself, you can find it here:
http://dev.monetdb.org/downloads/testing/

Comment 17974

Date: 2012-11-21 14:49:40 +0100
From: @sjoerdmullender

Oct2012-SP1 has been released.

@monetdb-team monetdb-team added bug Something isn't working major Server Tools labels Nov 30, 2020
@sjoerdmullender sjoerdmullender added this to the Ancient Release milestone Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major Server Tools
Projects
None yet
Development

No branches or pull requests

2 participants