Closed (cannot reproduce)
Project:
Drush SQL Sync Pipe
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jul 2013 at 17:33 UTC
Updated:
30 Aug 2016 at 23:01 UTC
Jump to comment: Most recent
Comments
Comment #1
markhalliwellIn theory, it should work with the "default" alias... but my guess is that I need to add support for detecting this... weird. Try explicitly setting the second alias parameter:
drush sql-sync-pipe @dev @local --progressComment #2
jbrown commentedError: no alias record could be found for @localWith sql-sync you can specify the sites directory. I think the destination is also optional for sql-sync.
Comment #3
markhalliwell@localwas just an example..... you have to have a local alias set up for this to work.I'm also pretty sure the destination argument is required for sql-sync as well.
Comment #4
jbrown commentedOkay - setup a local alias, but still getting the same almost non-existent transfer rate.
Is there any other information I could provide you with?
Comment #5
markhalliwellYou could send me the debug output via my contact form.
Comment #6
jbrown commentedokay I sent it.
Comment #7
fluxsauce commentedHi jbrown, I work at Pantheon and have been working with Mark on SSP support. He sent me the debug output; we didn't see anything obvious, and it doesn't look like a Drush version problem.
Are you certain that the site wasn't suspended at the time? In order to conserve resources, Pantheon temporarily suspends activity on environments that haven't gotten any traffic for a couple hours. When an environment is suspended, all services associated with that environment are suspended, including the database, cron and so forth.
Currently, we don't support MySQL socket activation, so in order to "wake up" the site, just visit the environment in question with a browser. It typically takes 15-30 seconds for a site to "wake up", during which time the browser will show that the page is still loading. After the initial "wake up", site performance should return to normal.
Does that help? Try visiting the remote site in question with a browser, then repeat the SSP operation.
Comment #8
jbrown commentedThis isn't the problem - I've been actively using the site before syncing the database.
I'm on Ubuntu if that helps.
Comment #9
fluxsauce commentedWhat's the @local alias look like? Assuming the @dev alias is just a renamed Pantheon alias?
Comment #10
scottrigbyI saw the same response while trying ssp --progress on a seriously crappy internet connection (while riding a bus!). In my case I knew there was a slim chance of it working, but tried anyway. As soon as I got back to a decent connection it worked like a charm.
As for alias, you can use @self when working locally.
Comment #11
jbrown commentedYeah - @dev is a renamed pantheon alias
@local is
Same problem with @self
Regardless of whether or not I use a VPN the problem is the same.
If I tether through the 3G on my phone the problem is also the same.
Comment #12
jbrown commentedNow it just exists immediately outputting:
Comment #13
mrfelton commentedI have the same problem. I can sync at normal speeds using pan-sql-sync.
Comment #14
elijah lynnJust installed this and am also getting very slow transfer speeds. 10-100Kbits (yes, bits)
I am also on Ubuntu, I did install the progress tool.
Comment #15
likewhoa commented^ confirmed above but import seems corrupt on my end.
this is with a 'drush -y sql-sync-pipe @pantheon.somesite.live @self --progress' which took 5m47.890s to complete for a 19.3MB db.
EDIT: after running the command a second time around, the db is ok so probably something happened during transfer or mysql import. There should be a feature to verify a checksum from remote to local db before hand.
Comment #16
markhalliwell@likewhoa, the only way to do a checksum is if the database was a file on both ends. Even if you were to do the
--dumpoption, you would still only have one file (locally) as the server would never contain a dump of the DB (hence the name of this project "pipe"). It's just an unfortunate side effect of this slow connection sometimes :(@FluxSauce, any progress on y'alls end to determine what could be causing this?
Comment #17
likewhoa commented@mark I understand that but having data transferred through a pipe can sometimes become corrupt. Perhaps a dump on the remote end should be done before hand to produce an md5sum so that it can be confirmed on both ends.
I will probably continue to use pan-sql-sync, I just came here to evaluate sql-sync-pipe for a project.
Comment #18
markhalliwell@likewhoa, as stated on the project's page under the history section:
There are use cases where dumping the db on the remote server is simply not possible (ie: takes up too much of the VM's disk space because their DB server is what has the filespace) or in the case of Pantheon, no access to the remote server (via normal ssh port, it was like this... not so sure about that anymore). I'm not discounting that there are indeed sometimes corrupt DB transfers due to network interference and timeouts, the same could be said for transferring a large dump file. Regardless, corrupt data typically has more to do with the network connection between the source and destination (or even the original source), not the method of traversal.
I can assure you that Pantheon has been working on simplifying this issue and have their own set of tools (https://www.getpantheon.com/blog/terminus-pantheon-cli). I'll likely integrate this at some point (or will accept patches to do so). This project actually originated before their set of tools came out and I had worked with them to get this working so it would connect directly to a pantheon DB (which is why pantheon added the
db-allows-remoteto their alias outputs).The point is: this is simply a different method for transferring a DB (much faster than standard sql-sync, aside from this very odd random pantheon connection bug). Every server has it's own configuration and workflow.
I'm glad you found a tool that works for you. This project is, by no means, the perfect solution for everything (and is relatively new). I typically am very forward thinking about new features, but I wanted to give you an explanation and reasoning behind why this decision was and currently is the way it is. If you feel the project page should be updated in some fashion that more accurately explains this, I am certainly open to suggestions.
Comment #19
likewhoa commented@mark thank you for the detailed explanation. Once the transfer rate is fixed upstream then I will consider using this tool as currently it's to slow for comfort compared to pandarus pan-sql-sync which took only 1min compared to 5mins with sql-sync-pipe. I hope pantheon gets this issue resolved.
Thanks again.
Comment #20
markhalliwell@likewhoa, you're very welcome :) I hope they do too. I'm hoping its something on their end they just need to tweak or some configuration option on the mysql connection I need to add. Regardless, I look forward to a solution soon.
FWIW, this tool isn't just for pantheon sites. It works well with most servers just like drush core's
sql-synccommand does. And those are much, much faster. I recommend trying it out on a server that isn't pantheon if you can ;) I'm sure you'll be impressed once it works properly (and more so if you have the progress viewer enabled).Comment #21
likewhoa commentedoh that I didn't even think of \o/ I will test on a non-pantheon server and yes I has pipeviewer :)
Comment #22
likewhoa commentedComment #23
marko b commentedI have the same problem with Pantheon, transfer is just too slow. I am trying
C:\wamp\www\KingTrivia>drush sql-sync-pipe @pantheon.kingtrivia1.dev @self --progress
and I don't get any progress indicator, drush prompt is just "blocked" and after 10 minutes it is over and it does work and I get new DB on localhost but this is just a 700 kb db and this is just too slow, right? I don't know how to check the speed and how to get any output of the speed. I am on DSL and internet connection isn't a issue.
Comment #24
thedavidmeister commentedYup, having the same issue ... this is terrible since Pantheon's own documentation recommends this module.
Comment #25
markhalliwellIs this even still an issue?
Comment #26
maq.said commentedI find extremely slow to import drupal database to Pantheon. My database size is 10 MB and I am using import button when setting up site for 1st time. Is there a better way to do it. Pantheon should be showing on-line tracker. Now it just shows time lapsed after process has started.
Comment #27
colanI haven't been able to reproduce this. Please reopen if someone can track this down.
Pantheon now recommends core sql-sync, and not sql-sync-pipe. See #2636320: Request that Pantheon recommend sql-sync-pipe for details.