Run a docker image initialisation hangs on azure containers

[serge calderara]

Dear all,

I have download to my local machine the docker image atlassian/jira-software:8.19.1-jdk11.
I can run it succesfully and initialisation is quite fast.

I did not change any settings, just running it as provided.

Then I try to deploy that image to Azure container registry and run the image from there.

I fully manage to deploy it and run it.

But what is wierd is that when the initialisation phase is starting, I have the feeling that it hangs on plugin initialisation, which is not occuring when running localy.

The last application log information I get from azure container log is as below :

memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 156 MiB. Committed: 371 MiB. Max: 1980 MiB
Non-heap memory : Used: 85 MiB. Committed: 137 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 241 MiB. Committed: 509 MiB. Max: 3516 MiB
---------------------------------------------------------------------------------
2021-10-15 09:17:03,995+0000 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [JIRA-STATS] [plugin-transaction] numberStartEvents:4, numberEndEvents:4, numberSendEvents:38, numberEventsInTransactions:1954, numberOfPluginEnableEvents:37
2021-10-15 09:22:03,995+0000 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [JIRA-STATS] [plugin-transaction] numberStartEvents:4, numberEndEvents:4, numberSendEvents:38, numberEventsInTransactions:1954, numberOfPluginEnableEvents:37
2021-10-15 09:27:03,995+0000 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [JIRA-STATS] [plugin-transaction] numberStartEvents:4, numberEndEvents:4, numberSendEvents:38, numberEventsInTransactions:1954, numberOfPluginEnableEvents:37
2021-10-15 09:32:03,995+0000 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [JIRA-STATS] [plugin-transaction] numberStartEvents:4, numberEndEvents:4, numberSendEvents:38, numberEventsInTransactions:1954, numberOfPluginEnableEvents:37

Any idea why plug in initialisation gets stuck when running the same local image on Azure ?

Thanks for help

regards

[Charlie Misonne]

Hi Serge,

Are you able to access the full logs:

• catalina log in the install directory
• atlassian-jira.log in the data directory

I think those could contains more useful log statements.

[serge calderara]

@Charlie Misonne I have access to logs yes but no error in it, sounds like a huge latency.

I have made a test that if I DO NOT mount any volume with jira for data storage, setups goes fast. Once I attached a file share it hangs

any experiment on your site by using atlassian image in azure?

[Charlie Misonne]

Perhaps the permissions of the volume are not right. The directory should be writable by the jira user (UID 2001). Try to connect to the container and check if this is the case.

I'm not a docker expert but there must be a way to fix those permissions.

[serge calderara]

@Charlie Misonne , I have check the file share and data are written there, no problem.

The only thing I notice is that the simple original instance of Jira running locally start and init fast. 

When run in azure the same image without any change take a long of time, the simple plug in initialisation takes roughtly 1 hour and during that time you get the picture below :

I satrt it at 1h30 and it is still not complete, the log is moving slowly, slowly

wierd

[Charlie Misonne]

That's odd

What kind of Azure storage are you using and on where are you mounting it (on which directory)?

[serge calderara]

its a standard SMB files share 

here is the command used to pull the atlassian image on Container Instance with volume mapping:

[Charlie Misonne]

The data directory of Jira must be on a fast disk. It contains indexes and caching. If you mount it over SMB it will be too slow. I think that's why you are encountering this performance issue.

Can't you use a local disk?
I have no experience with  Azure Container Instances so I'm not sure whether this is supported.