[ 
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor updated IGNITE-20971:
--------------------------
    Description: 
Creating 1000 tables with 5 column each.

*Expected:*
1000 tables are created.

 

*Actual:*

After some tables (in my case after 75 tables) the Ignite runner process is 
silently teared down, no any errors in output. GC log doesn't show any problem.

 

*Additional information:*

On more performant (in CPU) servers it can create up to 855 tables on 4GB HEAP 
and then tearing down with 
`java.lang.OutOfMemoryError: Java heap space`

  was:
Creating 1000 tables with 5 column each.

Expected:
1000 tables are created.

 

Actual:

After some tables (in my case after 75 tables) the Ignite runner process is 
silently teared down, no any errors in output. GC log doesn't show any problem.

 

Additional information:

On more performant (in CPU) servers it can create up to 855 tables on 4GB HEAP 
and then tearing down with 
`java.lang.OutOfMemoryError: Java heap space`


> The Ignite process quietly tear down while creating a lot of tables
> -------------------------------------------------------------------
>
>                 Key: IGNITE-20971
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20971
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 3.0.0-beta2
>            Reporter: Igor
>            Priority: Major
>              Labels: ignite-3
>
> Creating 1000 tables with 5 column each.
> *Expected:*
> 1000 tables are created.
>  
> *Actual:*
> After some tables (in my case after 75 tables) the Ignite runner process is 
> silently teared down, no any errors in output. GC log doesn't show any 
> problem.
>  
> *Additional information:*
> On more performant (in CPU) servers it can create up to 855 tables on 4GB 
> HEAP and then tearing down with 
> `java.lang.OutOfMemoryError: Java heap space`



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to