[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ]
Work on ISPN-7209 started by Ryan Emerson.
------------------------------------------
> Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
> ------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7209
> URL: https://issues.jboss.org/browse/ISPN-7209
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.0.0.Alpha4
> Reporter: Jiří Holuša
> Assignee: Ryan Emerson
>
> Given following scenario:
> 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache)
> 2) have the server configured to use JdbcStringBasedStore
> 3) used database is MariaDB 10
> Following exception is thrown:
> {code}
> ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
> {code}
> Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7209:
-------------------------------
Status: Open (was: New)
> Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB
> ------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7209
> URL: https://issues.jboss.org/browse/ISPN-7209
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.0.0.Alpha4
> Reporter: Jiří Holuša
> Assignee: Ryan Emerson
>
> Given following scenario:
> 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache)
> 2) have the server configured to use JdbcStringBasedStore
> 3) used database is MariaDB 10
> Following exception is thrown:
> {code}
> ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
> {code}
> Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ISPN-7272) Remove replication statistics from RpcManagerImpl
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7272:
----------------------------------
Summary: Remove replication statistics from RpcManagerImpl
Key: ISPN-7272
URL: https://issues.jboss.org/browse/ISPN-7272
Project: Infinispan
Issue Type: Task
Components: Core
Affects Versions: 8.1.6.Final, 9.0.0.Alpha4
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.0.0.Beta2
The replication statistics exposed by {{RpcManagerImpl}} are too low-level. For instance, in non-transactional caches, the times of the RPCs from the primary to the backups are counted both on the primary and on the originator (as part of the originator-to-primary RPC). They also aren't split by operation, like the {{CacheMgmtInterceptor}} statistics, which makes them even less useful.
The triangle algorithm changes things again, but only for distributed caches, so there is now one more way of interpreting the {{RpcManagerImpl}} statistics. It would be better to remove them altogether.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (ISPN-3731) Multicast messages can be replayed to new node
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3731?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3731:
-----------------------------------------------
Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1385162|https://bugzilla.redhat.com/show_bug.cgi?id=1385162] from ASSIGNED to POST
> Multicast messages can be replayed to new node
> ----------------------------------------------
>
> Key: ISPN-3731
> URL: https://issues.jboss.org/browse/ISPN-3731
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.0.Final
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Labels: 620, 630, 630betablocker
> Fix For: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Final
>
>
> Messages that target all current members are sent as multicast messages.
> However, these retransmissions can be replayed on new nodes that have just joined the cluster.
> This can result for example in execution of already completed transaction on the new node, causing possible data inconsistency for those entries which are owned by the new node in backup way - the replayed transaction sequence authoritatively overwrites them.
> The node should remember the first topologyId it has seen and do not execute any commands that have lower topologyId.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months