[teiid-issues] [JBoss JIRA] (TEIIDSB-121) cpu utilization on 100% when generate openapi doc by metadata

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIIDSB-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790183#comment-13790183 ] 

Steven Hawkins commented on TEIIDSB-121:
----------------------------------------

> We have 2 bad approach:

1. This is not necessarily a bad approach - you can always allocate a volume for this.  Not having access to any temp space will be an issue for this feature as the generated documents can be quite large and you don't want to have to regenerate them every time.

2. Due to the nature of the expansion to capture all of the odata options in openapi metadata coupled with using an xsl transformation mean that things can be problematic in terms of memory and in this case cpu utilization - there's a warning about that in the docs and in the original issue.

What we are looking to do with the Teiid Spring Boot / openshift tooling is to have everything related to metadata pre-generated for the runtime image.  This will include these openapi/swagger docs, so that it becomes a build time activity to generate them.  However I'm not sure when that will be ready.

In the meantime can you provide approximate details of your situation - number of tables / columns involved and any cpu/memory limits you have on your image so we can see if there are any obvious workarounds in the meantime.

> cpu utilization on 100% when generate openapi doc by metadata
> -------------------------------------------------------------
>
>                 Key: TEIIDSB-121
>                 URL: https://issues.jboss.org/browse/TEIIDSB-121
>             Project: Teiid Spring Boot
>          Issue Type: Bug
>          Components: datasource, OData
>    Affects Versions: 1.2.0
>            Reporter: Renat Eskenin
>            Priority: Major
>
> When i get request as 
> http://localhost:8080/odata/swagger.json or http://localhost:8080/odata/datasource/Account/swagger.json or http://localhost:8080/odata/datasource/swagger.json
> cpu utilization 100% and i do not get any response.
> We have 2 bad approach:
> 1. In org.teiid.olingo.web.OpenApiHandler:151 teiid create tmp file in filesystem.
> Its bad because in Docker k8s systems applications can't create any files in FS.
> 2. In org.apache.xalan.transformer.TransformerImpl:709 we get system freeze (CPU utilization 100% infinite)



--
This message was sent by Atlassian Jira
(v7.13.8#713008)