This is the same auto-configuration restart issue that I was referring to. As a work around I started an import with manual configuration and it is currently in progress now.
I have two major questions at this point of time.
We are in discussions to purchase the plugin as our trail is coming to end closely. What kind of support that an enterprise (licensed) customers get from TMATE if there are any issues in future during our migration journey. Is it the same way that we are discussing right now , or do we have a separate support channel/communications for licensed customers ?
From the mirror logs I observed that for every 1000 revisions it is doing a git GC, which is going on almost 2 hours and only after 2 hours the sync process is getting re-started.
Is it normal ? 2 to 3 hours of GC for every 1000 revisions ?
there are no add-on options in the Atlassian Marketplace that would inculde a dedicated support so all the SVN Mirror licenses available throug the Marketplace offer only Basic support which only includes support through open spaces on this forum with response during 3 working days.
However, we also have an extended Dedicated Support contract available for Euro 9900/year. In scope of the contract, we offer a dedicated private space on the support forum not visible to anybody else but our support and users you add explicitly, email support channel, 4 hours of voice support per year and guarnteed response during one working day. This contract is being sold separately, not throug the Atlassian Marketplace.
We also offer per-case support either through the email or forum option or using voice/video conferencing, here aer little more details:
As for the triggering GC every 1000 revisions – this is a default setting, so that is expected. The time needed for the garbage collection depends completely on the repository and what actions/changes were made in the commits, for some repositories and revisions 2 hours it’s pretty normal and expected. It’s too much for the import process, though, so I think it may worth to switch the GC off completely for the import or at least make it triggered less often. It can be done with the following setting:
[svn]
…
triggerGitGC = false
or
[svn]
…
triggerGitGC = <number of revisions>
This setting should be added right to the mapping configuration prior the initial import start. The former setting (false) switches GC completely, the latter tells the add-on to trigger GC every <number of revisions>.
Can I add the value “triggerGitGC = false” for the current import which is currently in-progress and apply changes ? Is that possible . Or if I add , will it restart the import process ?
At the same time , do we have any adverse affects of disabling GC
The setting won’t be applied on the fly, it needs to be applied explicitly by the button and the import has to be restarted (stopped and started again, not restarted from the very beginning) to apply this settings.
A possible drawback is that the repository may take more disk space rather that in case when GC is enabled. However, it’s only for the import time, after the initial import finished the setting can be switched back of the GC can be triggered manually in the repository.
unfortunately, the last log does not contain much information, just a process of translating some revision, not even clear which one. The process itself seems to run smooth, however.
The fact that the log has not been created may indicate that the process indeed stuck, so it worth try to stop the import with the Stop button and restart it a couple of minutes later.
Disappearing log is very strange issue since normally the add-on does not remove this file. Could you advise could any other process remove that file?
this error indicates the user interface (front-end application) has difficulties communicating with the backend. This often appears when some network communication problems are present, especially if the Bitbucket Server is being accessed over a VPN tunnel or over an SSH tunnel. Also, it may appear when there are problems using long polling mechanism, for example, if the web browser (or reverse proxy on the Bitbucket Server) does not support long polling. If any of the above may be present, it may worth trying to not to use long polling. To disable long polling de-select the “Use Long Polling” checkbox on the “Add-on settings” tab in global SVN Mirror setting:
I understand that, but I’m afraid there is no other way to change the setting but the settings in the UI. Do I understand correctly you are accessing the Bitbucket Server over a VPN tunnel? Could it be possible to do that from the local network where the server resides (at least to change the setting)? Also, have you tried to use another web-browser?
Is there a way we can change these settings from the server in any configuration file.
Why is this behaving this way suddenly ? It was working fine until Friday. Do you want to check any logs to understand this.
Does disable/enable (or) uninstall/install of the plugin will help ?
Did it happen with any customer before ?
As due to pandemic everybody is working remote , from what I understand everyone should be definately using company VPN right . I dont understand when you say local network . Do you mean should we be in the office location network which is hosting the bitbucket server ?
I’m kind of stuck and have 2 BIG repositories pending.
sure, we were trying to find a way to switch the Long Polling off in your situation. A possible way to do that is to use SVN Mirror add-on’s REST API, here is the request that switched the setting off:
Replace the USER, PASSWORD and BITBUCKET_SERVER_URL placeholders with correspondent user, password and the URL. If you don’t have cURL on your computer (which is usually true for Windows) use any other means to sent a POST request, for example, Postman software.
Also, I’d like to ask if it’s true that you have many web browser tabs or windows opened with SVN Mirror UI opened in those tabs? Such a situation may also disturb long polling operations and this may be the reason it does not work today while it worked last week.
could you please also add the -v cURL option, just to make sure the request went well:
curl -v -k -u…
What about the number of tabs, could it be the case you have too many of them opened? Also, could you please advise are Bitbucket Server pages available and work well and if only SVN Mirror add-on pages are affected?
we are investigating this right now, I’ll be keeping you informed.
Meanwhile, we could use the REST API for the mirroring operations, too, could you please advise what the changes or operations do you need to perform in repositories?
we continue investigating the issue, yet haven’t managed to re-produce it in our test environment. May I ask you to share Bitbucket and SVN Mirror logs with us to investigate? I’m afraid add-on’s Support ZIP feature is not much of a help currently, but it’s possible to collect it directly from the filesystem. Also, could you please advise what is your Bitbucket Server version and edition, how many node are in the cluster (if that is Datacenter cluster), and how did you install the add-on – have you installed it from Atlassian Marketplace or in some other way?