November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4811) Add Cross-Site state transfer operations and metrics to CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4811?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4811: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1158845|https://bugzilla.redhat.com/show_bug.cgi?id=1158845] from POST to MODIFIED > Add Cross-Site state transfer operations and metrics to CLI > ----------------------------------------------------------- > > Key: ISPN-4811 > URL: https://issues.jboss.org/browse/ISPN-4811 > Project: Infinispan > Issue Type: Sub-task > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Final > > > Add the operations to control the cross-site state transfer and the metrics to check the state of running state transfer to CLI. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4900) Split-brain: cancelled ST results in missing data

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4900?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4900: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Final Resolution: Done > Split-brain: cancelled ST results in missing data > ------------------------------------------------- > > Key: ISPN-4900 > URL: https://issues.jboss.org/browse/ISPN-4900 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Final > > Attachments: log.txt > > > 1. Cluster [A, B, C, D], in CH 1 segment X owned by [D, C] > 2. Split brain [A, B], [C, D]: A and B detects that D is missing, therefore they get view [A, B, C] and start rebalancing, in CH 2 segment X is owned by [C, B] > 3. A and B get new view [A, B] (C is missing) and state transfer of X is cancelled, nodes enter degraded mode. > 4. Split brain is fixed, all nodes find each other and merge - B starts to be AVAILABLE, but still does not have data for X > 5. Subsequent requests on B return null upon cache.get() -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4927) Bulk Ops in HotRod should use new implementations of keySet and entrySet

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4927?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4927: ------------------------------------- Assignee: Tristan Tarrant (was: William Burns) > Bulk Ops in HotRod should use new implementations of keySet and entrySet > ------------------------------------------------------------------------ > > Key: ISPN-4927 > URL: https://issues.jboss.org/browse/ISPN-4927 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4934) Upgrade to protostream-2.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4934: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1159815|https://bugzilla.redhat.com/show_bug.cgi?id=1159815] from NEW to ASSIGNED > Upgrade to protostream-2.0.1.Final > ---------------------------------- > > Key: ISPN-4934 > URL: https://issues.jboss.org/browse/ISPN-4934 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4934) Upgrade to protostream-2.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4934: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1159815 > Upgrade to protostream-2.0.1.Final > ---------------------------------- > > Key: ISPN-4934 > URL: https://issues.jboss.org/browse/ISPN-4934 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4877) Protostream: Invalid log format in SerializationContextImpl

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4877?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-4877. --------------------------------- Resolution: Done Fixed by ISPN-4907 > Protostream: Invalid log format in SerializationContextImpl > ----------------------------------------------------------- > > Key: ISPN-4877 > URL: https://issues.jboss.org/browse/ISPN-4877 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Trivial > Fix For: 7.0.0.Final > > > {noformat} > java.util.UnknownFormatConversionException: Conversion = '%' > at java.util.Formatter.checkText(Formatter.java:2579) > at java.util.Formatter.parse(Formatter.java:2565) > at java.util.Formatter.format(Formatter.java:2501) > at java.util.Formatter.format(Formatter.java:2455) > at java.lang.String.format(String.java:2927) > at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:434) > at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:397) > at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:568) > at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:225) > at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) > at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:79) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:296) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.Logger.logRaw(Logger.java:721) > at org.jboss.logmanager.Logger.log(Logger.java:672) > at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50) > at org.jboss.logging.Logger.logf(Logger.java:2112) > at org.jboss.logging.DelegatingBasicLogger.debugf(DelegatingBasicLogger.java:234) > at org.infinispan.protostream.impl.SerializationContextImpl.registerFileDescriptor(SerializationContextImpl.java:125) > at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:88) > at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:104) > at org.infinispan.protostream.ProtobufUtil.newSerializationContext(ProtobufUtil.java:33) > at org.infinispan.query.remote.ProtobufMetadataManager.<init>(ProtobufMetadataManager.java:65) > at org.infinispan.query.remote.LifecycleManager.initProtobufMetadataManager(LifecycleManager.java:54) > at org.infinispan.query.remote.LifecycleManager.cacheManagerStarted(LifecycleManager.java:50) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:230) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:430) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4877) Protostream: Invalid log format in SerializationContextImpl

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4877?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4877: -------------------------------- Status: Open (was: New) > Protostream: Invalid log format in SerializationContextImpl > ----------------------------------------------------------- > > Key: ISPN-4877 > URL: https://issues.jboss.org/browse/ISPN-4877 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Trivial > Fix For: 7.0.0.Final > > > {noformat} > java.util.UnknownFormatConversionException: Conversion = '%' > at java.util.Formatter.checkText(Formatter.java:2579) > at java.util.Formatter.parse(Formatter.java:2565) > at java.util.Formatter.format(Formatter.java:2501) > at java.util.Formatter.format(Formatter.java:2455) > at java.lang.String.format(String.java:2927) > at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:434) > at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:397) > at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:568) > at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:225) > at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) > at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:79) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:296) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:304) > at org.jboss.logmanager.Logger.logRaw(Logger.java:721) > at org.jboss.logmanager.Logger.log(Logger.java:672) > at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50) > at org.jboss.logging.Logger.logf(Logger.java:2112) > at org.jboss.logging.DelegatingBasicLogger.debugf(DelegatingBasicLogger.java:234) > at org.infinispan.protostream.impl.SerializationContextImpl.registerFileDescriptor(SerializationContextImpl.java:125) > at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:88) > at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:104) > at org.infinispan.protostream.ProtobufUtil.newSerializationContext(ProtobufUtil.java:33) > at org.infinispan.query.remote.ProtobufMetadataManager.<init>(ProtobufMetadataManager.java:65) > at org.infinispan.query.remote.LifecycleManager.initProtobufMetadataManager(LifecycleManager.java:54) > at org.infinispan.query.remote.LifecycleManager.cacheManagerStarted(LifecycleManager.java:50) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:230) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:430) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89) > at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4678) Trim down ExpandableMarshalledValueByteStream to the actual data length before storing in cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4678?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4678: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1122631|https://bugzilla.redhat.com/show_bug.cgi?id=1122631] from NEW to MODIFIED > Trim down ExpandableMarshalledValueByteStream to the actual data length before storing in cache > ----------------------------------------------------------------------------------------------- > > Key: ISPN-4678 > URL: https://issues.jboss.org/browse/ISPN-4678 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.CR1 > > > When storeAsBinary configuration flag is used, the ExpandableMarshalledValueByteStream is used to serialize objects to byte arrays. > However, for value size up to 4kB, almost half of the space for each cache entry can be wasted because the ByteStream is stored as is - with the additional space for future expansion. > For value size greater than 4kB, only additional 25% of actual value size can be wasted. But as these values can be quite large, the wasted space gets bigger too. > It is not necessary to store ExpandableMarshalledValueByteStream as is and can be shrinked to actual data size before storing in cache. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4934) Upgrade to protostream-2.0.1.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4934?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4934: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3042 > Upgrade to protostream-2.0.1.Final > ---------------------------------- > > Key: ISPN-4934 > URL: https://issues.jboss.org/browse/ISPN-4934 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4907) Upgrade to protostream-2.0.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4907?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4907: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1158882|https://bugzilla.redhat.com/show_bug.cgi?id=1158882] from ASSIGNED to MODIFIED > Upgrade to protostream-2.0.0.Final > ---------------------------------- > > Key: ISPN-4907 > URL: https://issues.jboss.org/browse/ISPN-4907 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2014