September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-12309) Creating cache with invalid configuration leaves inconsistent state

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12309?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12309: ------------------------------------- Summary: Creating cache with invalid configuration leaves inconsistent state (was: Invalid indexed type is breaking the console) > Creating cache with invalid configuration leaves inconsistent state > ------------------------------------------------------------------- > > Key: ISPN-12309 > URL: https://issues.redhat.com/browse/ISPN-12309 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Katia Aresti > Assignee: Gustavo Fernandes > Priority: Major > > _see desc in the linked issue_ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12319) XSite Response should allow a value

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12319?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12319: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev04 (was: 12.0.0.Final) Resolution: Done > XSite Response should allow a value > ----------------------------------- > > Key: ISPN-12319 > URL: https://issues.redhat.com/browse/ISPN-12319 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Dev04 > > > Currently cross site does not allow for a response. This will be needed for operations such as max idle cross site as we may have to know if a value has expired in the other site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12309) Invalid indexed type is breaking the console

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12309?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12309: -------------------------------- Description: _see desc in the linked issue_ > Invalid indexed type is breaking the console > -------------------------------------------- > > Key: ISPN-12309 > URL: https://issues.redhat.com/browse/ISPN-12309 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Katia Aresti > Assignee: Gustavo Fernandes > Priority: Major > > _see desc in the linked issue_ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12309) Invalid indexed type is breaking the console

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12309?page=com.atlassian.jira.plugi... ] Katia Aresti reassigned ISPN-12309: ----------------------------------- Assignee: Gustavo Fernandes (was: Katia Aresti) > Invalid indexed type is breaking the console > -------------------------------------------- > > Key: ISPN-12309 > URL: https://issues.redhat.com/browse/ISPN-12309 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Katia Aresti > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12326) CLI command "report" generates a single Thread Dump

by Varsha Sharma (Jira)

[ https://issues.redhat.com/browse/ISPN-12326?page=com.atlassian.jira.plugi... ] Varsha Sharma updated ISPN-12326: --------------------------------- Description: "report" command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. To debug unresponsiveness, its always advisable to capture multiple thread dumps, so if the command capture multiple thread dumps it can be useful to check thread status transition. was: "report" command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. It should capture multiple thread dumps at a specified interval(say 10 sec) Multiple thread dumps can be useful to check thread status transition. > CLI command "report" generates a single Thread Dump > --------------------------------------------------- > > Key: ISPN-12326 > URL: https://issues.redhat.com/browse/ISPN-12326 > Project: Infinispan > Issue Type: Enhancement > Components: Tasks > Affects Versions: 11.0.3.Final > Reporter: Varsha Sharma > Priority: Minor > > "report" command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. > Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. > To debug unresponsiveness, its always advisable to capture multiple thread dumps, so if the command capture multiple thread dumps it can be useful to check thread status transition. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12326) CLI command "report" generates a single Thread Dump

by Varsha Sharma (Jira)

[ https://issues.redhat.com/browse/ISPN-12326?page=com.atlassian.jira.plugi... ] Varsha Sharma updated ISPN-12326: --------------------------------- Description: "report" command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. It should capture multiple thread dumps at a specified interval(say 10 sec) Multiple thread dumps can be useful to check thread status transition. was: In Data Grid 8.1 report command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. It should capture multiple thread dumps at a specified interval(say 10 sec) Multiple thread dumps can be useful to check thread status transition. -rw-rw-r--. 1 vasharma vasharma 190300 Sep 15 13:29 red-hat-data-grid-vasharma-11430-20200915132918-report.tar.gz drwxrwxr-x. 2 vasharma vasharma 4096 Sep 15 10:53 20537 $ cd 20537/ [ 20537]$ ll total 0 -rw-rw-r--. 1 vasharma vasharma 0 Sep 15 10:53 thread-dump [https://access.redhat.com/documentation/en-us/red_hat_data_grid/8.1/html-...] > CLI command "report" generates a single Thread Dump > --------------------------------------------------- > > Key: ISPN-12326 > URL: https://issues.redhat.com/browse/ISPN-12326 > Project: Infinispan > Issue Type: Enhancement > Components: Tasks > Affects Versions: 11.0.3.Final > Reporter: Varsha Sharma > Priority: Minor > > "report" command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. > Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. > It should capture multiple thread dumps at a specified interval(say 10 sec) > Multiple thread dumps can be useful to check thread status transition. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12326) CLI command "report" generates a single Thread Dump

by Varsha Sharma (Jira)

[ https://issues.redhat.com/browse/ISPN-12326?page=com.atlassian.jira.plugi... ] Varsha Sharma updated ISPN-12326: --------------------------------- Summary: CLI command "report" generates a single Thread Dump (was: CLI command "report" in Data Grid 8.1 generates a single Thread Dump) > CLI command "report" generates a single Thread Dump > --------------------------------------------------- > > Key: ISPN-12326 > URL: https://issues.redhat.com/browse/ISPN-12326 > Project: Infinispan > Issue Type: Enhancement > Components: Tasks > Affects Versions: 11.0.3.Final > Reporter: Varsha Sharma > Priority: Minor > > In Data Grid 8.1 report command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. > Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. > It should capture multiple thread dumps at a specified interval(say 10 sec) > Multiple thread dumps can be useful to check thread status transition. > -rw-rw-r--. 1 vasharma vasharma 190300 Sep 15 13:29 red-hat-data-grid-vasharma-11430-20200915132918-report.tar.gz > drwxrwxr-x. 2 vasharma vasharma 4096 Sep 15 10:53 20537 > $ cd 20537/ > [ 20537]$ ll > total 0 > -rw-rw-r--. 1 vasharma vasharma 0 Sep 15 10:53 thread-dump > [https://access.redhat.com/documentation/en-us/red_hat_data_grid/8.1/html-...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12326) CLI command "report" in Data Grid 8.1 generates a single Thread Dump

by Varsha Sharma (Jira)

Varsha Sharma created ISPN-12326: ------------------------------------ Summary: CLI command "report" in Data Grid 8.1 generates a single Thread Dump Key: ISPN-12326 URL: https://issues.redhat.com/browse/ISPN-12326 Project: Infinispan Issue Type: Enhancement Components: Tasks Affects Versions: 11.0.3.Final Reporter: Varsha Sharma In Data Grid 8.1 report command generates a server report which contains information such as thread dumps, memory configuration etc which can be used for troubleshooting deployment issues. Only Single thread dump is generated with this command which will only reflect information of threads at that particular moment . One thread dump may not help. It should capture multiple thread dumps at a specified interval(say 10 sec) Multiple thread dumps can be useful to check thread status transition. -rw-rw-r--. 1 vasharma vasharma 190300 Sep 15 13:29 red-hat-data-grid-vasharma-11430-20200915132918-report.tar.gz drwxrwxr-x. 2 vasharma vasharma 4096 Sep 15 10:53 20537 $ cd 20537/ [ 20537]$ ll total 0 -rw-rw-r--. 1 vasharma vasharma 0 Sep 15 10:53 thread-dump [https://access.redhat.com/documentation/en-us/red_hat_data_grid/8.1/html-...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12325) Hot Rod server instances in tests use too much memory

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12325?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12325: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8690 > Hot Rod server instances in tests use too much memory > ----------------------------------------------------- > > Key: ISPN-12325 > URL: https://issues.redhat.com/browse/ISPN-12325 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev04 > > > When a test class finishes, TestNG does not discard the test instance, instead it keeps it in memory until the test suite finishes. This means test class fields that uses a lot of memory will accumulate in memory, making the test suite use a lot more heap than it should. > ISPN-8478 added a generic way to set {{Cache}} and {{EmbeddedCacheManager}} fields to {{null}} in order to reduce memory usage, but hotrod-client tests do not have anything similar for {{HotRodServer}} and {{RemoteCacheManager}} fields. > That might need to change: hotrod-client tests often keep references to {{HotRodServer}} instances in fields, and the servers use > 3MB, most of it in the {{SerializationContextRegistryImpl}}: > {noformat} > Class Name | Shallow Heap | Retained Heap | Percentage > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > org.infinispan.client.hotrod.ReplTopologyChangeTest @ 0xc52bf018 | 96 | 10,358,136 | 1.02% > |- org.infinispan.server.hotrod.test.HotRodTestingUtil$1 @ 0xe30cc538 | 128 | 3,420,600 | 0.34% > | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl @ 0xcd18d210 | 24 | 2,493,584 | 0.25% > | | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl$MarshallerContext @ 0xe3d18c08| 32 | 2,358,320 | 0.23% > | | | |- org.infinispan.protostream.impl.SerializationContextImpl @ 0xe3d18e78 | 64 | 2,357,696 | 0.23% > | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe3d67fe0 | 72 | 967,680 | 0.10% > | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe41b8798 | 72 | 690,528 | 0.07% > | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc997eaf8 | 72 | 413,376 | 0.04% > | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed3cd8 | 72 | 214,640 | 0.02% > | | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed4b60 | 72 | 183,648 | 0.02% > | | | | | | | | | |- org.infinispan.protostream.descriptors.Descriptor @ 0xc5edabe8 | 72 | 132,104 | 0.01% > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12325) Hot Rod server instances in tests use too much memory

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12325?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12325: -------------------------------- Status: Open (was: New) > Hot Rod server instances in tests use too much memory > ----------------------------------------------------- > > Key: ISPN-12325 > URL: https://issues.redhat.com/browse/ISPN-12325 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev04 > > > When a test class finishes, TestNG does not discard the test instance, instead it keeps it in memory until the test suite finishes. This means test class fields that uses a lot of memory will accumulate in memory, making the test suite use a lot more heap than it should. > ISPN-8478 added a generic way to set {{Cache}} and {{EmbeddedCacheManager}} fields to {{null}} in order to reduce memory usage, but hotrod-client tests do not have anything similar for {{HotRodServer}} and {{RemoteCacheManager}} fields. > That might need to change: hotrod-client tests often keep references to {{HotRodServer}} instances in fields, and the servers use > 3MB, most of it in the {{SerializationContextRegistryImpl}}: > {noformat} > Class Name | Shallow Heap | Retained Heap | Percentage > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > org.infinispan.client.hotrod.ReplTopologyChangeTest @ 0xc52bf018 | 96 | 10,358,136 | 1.02% > |- org.infinispan.server.hotrod.test.HotRodTestingUtil$1 @ 0xe30cc538 | 128 | 3,420,600 | 0.34% > | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl @ 0xcd18d210 | 24 | 2,493,584 | 0.25% > | | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl$MarshallerContext @ 0xe3d18c08| 32 | 2,358,320 | 0.23% > | | | |- org.infinispan.protostream.impl.SerializationContextImpl @ 0xe3d18e78 | 64 | 2,357,696 | 0.23% > | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe3d67fe0 | 72 | 967,680 | 0.10% > | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe41b8798 | 72 | 690,528 | 0.07% > | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc997eaf8 | 72 | 413,376 | 0.04% > | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed3cd8 | 72 | 214,640 | 0.02% > | | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed4b60 | 72 | 183,648 | 0.02% > | | | | | | | | | |- org.infinispan.protostream.descriptors.Descriptor @ 0xc5edabe8 | 72 | 132,104 | 0.01% > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020