-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Startup takes over 40 seconds on macOS Sierra #6047
Comments
That's odd. Can you try adding the option After which console/log message (if any) is it taking the 40 seconds? |
|
Ok if my memory serves me right, that's the same symptom which we've had the previous time. I'll try a bit more to find the other issue. GitHub search isn't too great... |
Found it: #4600 Can you try restarting your computer and see if the issue persists? (if you haven't done so already) |
I have setup one of the computers in our office on MacOS Sierra and am not able to reproduce this issue on either the current [1] Side note: I am not a fan of |
Just rebooted, and still seeing the same behavior. I am guessing this is related to macOS Sierra. How can I tell what is happening during these 40 or so seconds? |
You could try sending us the output of
Note that there are two things you need to do first to make sure this goes well:
Then send the spindump to either But I don't think that this is a generic issue on Sierra. |
Where do I run:
I.E. what should be the current working dir to invoke |
sorry... I forgot to modify that. Please remove the
|
I don't think it is working right, I have to
|
It looks like you are using a shell other than |
I am using |
Different shells do things differently. I just worked out what |
@larkost, just e-mailed the spindump to you and @danielmewes. Let me know what you find. Thanks so much! |
The spindup confirms that you are having network translation issues (specifically in But on a more general level, this is very unlikely to be an actual problem in our code, and more likely to be some bad interaction between MacOS Sierra and something else on your network (my money would be on something mDNS related, like an old AppleTV or AirPort router). @danielmewes: should we make this report an effort to report when it takes, say 5 or 10 seconds to do that? |
Let's merge this with #4600 . It still seems like a fairly rare issue (hence low priority), but we should keep an eye on it and prioritize it more if it hits more people. |
@danielmewes I just updated to Sierra and I'm seeing the exact same issue. Running on a MacBook Pro (early 2015). Was fine in El Capitan... @nodesocket I don't suppose you figured out a workaround? |
Ah, that's a shame. Have you tried uninstalling from |
...never mind – don't bother! It doesn't change anything. |
I just ran into this yesterday. RethinkDB worked fine under El Capitan. I did a clean install of Sierra over the weekend and installed RethinkDB from scratch and now it takes forever to boot. |
I just got the chance to work on my project again, and RethinkDB all the sudden works fine now. |
Just throwing this out there. Could that be related to RethinkDB taking a long time to startup? |
On OS X it uses kqueue. I noticed that I had the problem at first at home but then it went away. Then I went to Starbucks today, and there had the slow startup again. But then it went away. |
So... I had no issue a couple of days ago, and suddenly I was having this issue consistently. Here is how I fixed: I realized I recently renamed my computer. What I had done: And then I realized a bunch of caches might be influenced by this. I googled a bit and found this commands to set the name in different ways:
Reboot, and the issue is gone. |
Awesome. That has fixed the issue for me! Thanks for sharing @irae. |
In particular, it seems to be HostName that causes issues. It was unset for me. As soon as I gave it a value the delay went away completely. Did not have to reboot, and I did not touch the other values. On 10.12.2 at the time of writing. Could this perhaps be related to the default server name generation algorithm? |
We have also been having this issue while running rethinkdb 2.3.5 and macOS Sierra. Looks like this might be fixed with openstf/stf#509 but wanted to leave some bread crumbs in case someone else hits what we ran into. Thanks! |
No, that was a separate issue. There is a real delay in RethinkDB that is
apparent on both macOS without the hostname setting and on Linux when DNS
is very slow to respond. It's unfortunate that the dependency on DNS cannot
be disabled by specifying everything manually.
…On Fri, Mar 10, 2017 at 3:37 Zach Peterson ***@***.***> wrote:
We have also been having this issue while running rethinkdb 2.3.5 and
macOS Sierra.
The solution seems to have been what sorccu pointed out with
sudo scutil --set HostName [new name]
One gotcha we ran into was to make sure your host name does not include a
. character.
Our default host names were user-mac.local and once we removed the . it
seemed to work fine.
Looks like this might be fixed with openstf/stf#509
<openstf/stf#509> but wanted to leave some
bread crumbs in case someone else hits what we ran into.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6047 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-_TjfTrzd2SAdipmdvSRJkKHqS8Kuks5rkEbqgaJpZM4JjLEK>
.
|
guess this should be the root cause of this issue on Mac, so it's not related to the hostname setting on Mac, though... I don't have a proper solution to the problem yet. REF: |
Thanks!!! Ran into this issue. I reinstalled my OSX, and the rethinkdb was slow to load. I ran Thanks for that explanation @oldlam |
I had Running |
Starting up Rethinkdb
2.3.4
on the beta of macOS Sierra takes over 40 seconds even with no data. Any idea what could be happening? Installed RethinkDB viabrew
.Here is the configuration I am using:
The text was updated successfully, but these errors were encountered: