Re: ipropd slow when pushing complete database

Maybe 5 minutes is to be expected. What are others seeing as the time it 
takes a slave to pull down a complete database using iprop?



On 12/19/2018 10:21 AM, [email protected] wrote:
> I sometimes push the entire master database to a replica. I do this 
> using ipropd. The process is to stop ipropd-slave on the slave, delete 
> the database and log files, and then restart the ipropd-slave service. 
> The entire database is then pushed to the slave.
> 
> When pushing the database via ipropd to a traditional VM the process 
> takes a very long time, upwards of 5 to 6 *minutes*. I also get these 
> speeds when pushing to a stretch container running as a slave. In the 
> past, when using Heimdal 7.1 and pushing to a jessie container, the 
> speed was quite fast, around 10 seconds.
> 
> For comparison, I did an scp of a copy of the database file from the 
> master to the slave, and that only took about 6 seconds.
> 
> I realize that doing an ssh copy is not at all the same thing as doing 
> an ipropd copy from version 0, but something must be wrong if the ipropd 
> copy is 50 to 60 times slower.
> 
> I am running Heimdal version 7.5 on Debian stretch machines. The 
> database file is around 430 MB and the log file is around 23MB.
> 
> Anyone have any troubleshooting steps to find out why ipropd is so slow?
> 
> Thanks, Adam Lewenberg
> 
> 
> 
> 
> 
> 
>