June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9187) Lost segments logged when node leaves during rebalance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9187?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9187: ---------------------------------- Sprint: Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.CR1) > Lost segments logged when node leaves during rebalance > ------------------------------------------------------ > > Key: ISPN-9187 > URL: https://issues.jboss.org/browse/ISPN-9187 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.3.Final, 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > When a node leaves during rebalance, we remove the leaver from the current CH and from the pending CH with {{ConsistentHashFactory.updateMembers()}}. However, since the 4-phase rebalance changes joiners are also removed from the pending CH. > In the following log numOwners=2 and pending CH had one segment (239) owned by a joiner (D) and a leaver (B). The updated pending CH doesn't have either B or D, this means both owners are lost and random owners (C and A) are elected. A sees that it was allocated new segments from {{updateMembers}} and logs that the segment has been lost: > {noformat} > 08:53:01,528 INFO (remote-thread-test-NodeA-p2-t6:[cluster-listener]) [CLUSTER] [Context=cluster-listener] ISPN100002: Starting rebalance with members [test-NodeA-15001, test-NodeB-55628, test-NodeC-62395, test-NodeD-29215], phase READ_OLD_WRITE_ALL, topology id 10 > 08:53:01,554 TRACE (transport-thread-test-NodeD-p28-t2:[Topology-cluster-listener]) [CacheTopology] Current consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248-250 252 254}, backup: {... 235-236 243 246-247 251 253} > test-NodeB-55628 primary: {... 231 234 240 242}, backup: {... 232-233 239 241 255} > test-NodeC-62395 primary: {... 232-233 235-236 239 241 243 246-247 251 253 255}, backup: {... 231 234 237-238 240 242 244-245 248-250 252 254} > 08:53:01,554 TRACE (transport-thread-test-NodeD-p28-t2:[Topology-cluster-listener]) [CacheTopology] Pending consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 245 248 252}, backup: {... 235-236 244 246-247 251} > test-NodeB-55628 primary: {... 231 240 242}, backup: {... 230 239 241} > test-NodeC-62395 primary: {... 232-233 235-236 241 243 246-247 251 253 255}, backup: {... 231 234 240 242 245 249-250 252 254} > test-NodeD-29215 primary: {... 234 239 244 249-250 254}, backup: {... 232-233 237-238 243 248 253 255} > 08:53:01,606 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [ClusterCacheStatus] Removed node test-NodeB-55628 from cache cluster-listener: members = [test-NodeA-15001, test-NodeC-62395, test-NodeD-29215], joiners = [test-NodeD-29215] > 08:53:01,611 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [CacheTopology] Current consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248-250 252 254}, backup: {... 235-236 243 246-247 251 253} > test-NodeC-62395 primary: {... 230-236 239-243 246-247 251 253 255}, backup: {... 237-238 244-245 248-250 252 254} > 08:53:01,611 TRACE (remote-thread-test-NodeA-p2-t5:[cluster-listener]) [CacheTopology] Pending consistent hash's routing table: test-NodeA-15001 primary: {... 237-238 244-245 248 252}, backup: {... 235-236 239 246-247 251} > test-NodeC-62395 primary: {... 227-236 239-243 246-247 249-251 253-255}, backup: {... 226 245 252} > 08:53:01,613 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateTransferManagerImpl] Installing new cache topology CacheTopology{id=11, phase=READ_OLD_WRITE_ALL, rebalanceId=4, currentCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 134+45, test-NodeC-62395: 122+50]}, pendingCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 129+45, test-NodeC-62395: 127+28]}, unionCH=DefaultConsistentHash{ns=256, owners = (2)[test-NodeA-15001: 134+62, test-NodeC-62395: 122+68]}, actualMembers=[test-NodeA-15001, test-NodeC-62395, test-NodeD-29215], persistentUUIDs=[0506cc27-9762-4703-ad56-6a3bf7953529, c365b93f-e46c-4f11-ab46-6cafa2b2d92b, d3f21b0d-07f2-4089-b160-f754e719de83]} on cache cluster-listener > 08:53:01,662 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: new segments: {1-18 21 30-53 56-63 67 69-73 75-78 81-85 88-101 107-115 117-118 125-134 136-139 142-156 158-165 168-170 172-174 177-179 181-188 193-211 214-226 228-229 235-239 243-254}; old segments: {1-15 30-53 56-63 69-73 75-77 81-85 88-101 107-115 117-118 125-131 136-139 142-145 150-156 158-165 168-170 172-174 177-179 183-188 193-211 214-218 220-226 228-229 235-238 243-254} > 08:53:01,663 TRACE (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: added segments: {16-18 21 67 78 132-134 146-149 181-182 219 239}; removed segments: {} > 08:53:01,663 DEBUG (transport-thread-test-NodeA-p4-t1:[Topology-cluster-listener]) [StateConsumerImpl] Not requesting segments {16-18 21 67 78 132-134 146-149 181-182 219 239} because the last owner left the cluster > {noformat} > There isn't any visible inconsistency: A only owns segment 239 for writing, and the coordinator immediately starts a new rebalance, ignoring the pending CH that it sent out earlier. However, the new rebalance causes its own problems: ISPN-8240. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-375) Enable Hot Rod clients to start transactions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-375?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant updated ISPN-375: --------------------------------- Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Enable Hot Rod clients to start transactions > -------------------------------------------- > > Key: ISPN-375 > URL: https://issues.jboss.org/browse/ISPN-375 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 9.3.0.Final > > > It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only. > This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction. > Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7940) Deprecate Compatibility Mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7940?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7940: ---------------------------------- Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Deprecate Compatibility Mode > ---------------------------- > > Key: ISPN-7940 > URL: https://issues.jboss.org/browse/ISPN-7940 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.3.0.Final > > > Compatibility Mode should be marked for removal and internally all the remaining usages should be routed to the related encoder -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9020) Remote query: disabling indexing for a type with @Indexed(false) still creates empty documents in index

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9020?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9020: ---------------------------------- Sprint: Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.CR1) > Remote query: disabling indexing for a type with @Indexed(false) still creates empty documents in index > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-9020 > URL: https://issues.jboss.org/browse/ISPN-9020 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > When adding to cache protobuf encoded entries of types that are specifically annotated as @Indexed(false) we would expect that nothing is added to the index. But a document with no fields is added instead, cluttering the index. This does not impact the correctness of query results but it impacts performance because every put operation touches the index even if not required. This bug is a consequence of some limitations of the integration point between infinispan and hibernate search: the FieldBridge api. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9036: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9037) Release Docker images from CI

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9037?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9037: ---------------------------------- Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Release Docker images from CI > ----------------------------- > > Key: ISPN-9037 > URL: https://issues.jboss.org/browse/ISPN-9037 > Project: Infinispan > Issue Type: Enhancement > Components: Build, OpenShift > Reporter: Tristan Tarrant > Assignee: Osni Oliveira > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8234: ---------------------------------- Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema > ------------------------------------------------------------------------------ > > Key: ISPN-8234 > URL: https://issues.jboss.org/browse/ISPN-8234 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8997) Publish maven snapshot artifacts on stable master builds

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8997?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8997: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Publish maven snapshot artifacts on stable master builds > -------------------------------------------------------- > > Key: ISPN-8997 > URL: https://issues.jboss.org/browse/ISPN-8997 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Sebastian Łaskawiec > > Successful builds of the master branch should publish snapshot artifacts to Maven -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7979) Include all component licenses in distributions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7979?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7979: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1) > Include all component licenses in distributions > ----------------------------------------------- > > Key: ISPN-7979 > URL: https://issues.jboss.org/browse/ISPN-7979 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Jakub Senko > Priority: Blocker > Fix For: 9.3.0.Final > > > The distributions should include licenses for all components -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9259) Feature-packs should utilise modules/system/add-ons dir

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9259?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9259: ------------------------------- Status: Open (was: New) > Feature-packs should utilise modules/system/add-ons dir > ------------------------------------------------------- > > Key: ISPN-9259 > URL: https://issues.jboss.org/browse/ISPN-9259 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 9.3.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > Currently the feature-packs install infinispan modules in the root /modules dir, instead they should be stored under /modules/system/add-ons as per the [guidelines|https://developer.jboss.org/wiki%20/LayeredDistributionsAndMod...]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018