[JBoss JIRA] (ISPN-9847) Extend configuration to allow inline JGroups configuration and inheritance
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-9847:
-------------------------------------
Summary: Extend configuration to allow inline JGroups configuration and inheritance
Key: ISPN-9847
URL: https://issues.jboss.org/browse/ISPN-9847
Project: Infinispan
Issue Type: Bug
Components: Configuration, Core
Affects Versions: 10.0.0.Alpha2
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta1
Allowing inline JGroups configurations to increase usability.
Also support the following extra features:
* stack inheritance with protocol replacement/override
* easier xsite configuration
{code:xml}
<jgroups transport="org.infinispan.remoting.transport.jgroups.JGroupsTransport">
<!-- Load external JGroups stacks -->
<stack-file name="udp" path="stacks/udp.xml"/>
<stack-file name="tcp" path="stacks/tcp.xml"/>
<!-- Inline definition -->
<stack name="mping">
<TCP bind_port="7800" port_range="30" recv_buf_size="20000000" send_buf_size="640000"
sock_conn_timeout="300" bundler_type="no-bundler"
thread_pool.min_threads="0" thread_pool.max_threads="25" thread_pool.keep_alive_time="5000"/>
<MPING bind_addr="127.0.0.1" break_on_coord_rsp="true"
mcast_addr="${jgroups.mping.mcast_addr:228.2.4.6}"
mcast_port="${jgroups.mping.mcast_port:43366}"
ip_ttl="${jgroups.udp.ip_ttl:2}"/>
<MERGE3/>
<FD_SOCK/>
<FD_ALL timeout="3000"
interval="1000"
timeout_check_interval="1000"
/>
<VERIFY_SUSPECT timeout="1000"/>
<pbcast.NAKACK2
use_mcast_xmit="false"
xmit_interval="100"
xmit_table_num_rows="50"
xmit_table_msgs_per_row="1024"
xmit_table_max_compaction_time="30000"/>
<UNICAST3
xmit_interval="100"
xmit_table_num_rows="50"
xmit_table_msgs_per_row="1024"
xmit_table_max_compaction_time="30000"
/>
<RSVP />
<pbcast.STABLE stability_delay="200"
desired_avg_gossip="2000"
max_bytes="1M"
/>
<pbcast.GMS print_local_addr="false"
join_timeout="${jgroups.join_timeout:2000}"/>
<MFC max_credits="2M" min_threshold="0.40"/>
<FRAG3/>
</stack>
<!-- Use the "tcp" stack but override some protocol attributes -->
<stack name="mytcp" extends="tcp">
<MERGE3 max_interval="20000"/>
</stack>
<!-- Use the "tcp" stack but replace the discovery -->
<stack name="tcpgossip" extends="tcp">
<TCPGOSSIP initial_hosts="${jgroups.tunnel.gossip_router_hosts:localhost[12001]}" stack.combine="replace:TCP_NIO2"/>
</stack>
<!-- Add a relay configuration using a previously declared stack to talk to the remote site -->
<stack name="xsite" extends="udp">
<relay site="LON">
<remote-site name="NYC" stack="tcpgossip"/>
</relay>
</stack>
</jgroups>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9846) Ensure Backwards Compatibility with Persistence SPI changes
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9846?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9846:
-------------------------------
Status: Open (was: New)
> Ensure Backwards Compatibility with Persistence SPI changes
> -----------------------------------------------------------
>
> Key: ISPN-9846
> URL: https://issues.jboss.org/browse/ISPN-9846
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> ISPN-9693 deprecated the {{org.infinispan.marshall.core.MarshalledEntry}} interface in favour of {{org.infinispan.persistence.spi.MarshalledEntry}}, however this breaks compatibility with 9.4.x stores as the method signatures of the various store/loader interfaces changed.
> Therefore, to aid with enabling backwards compatibility it is necessary to change {{spi.MarshalledEntry}} to {{spi.MarshallableEntry}} as well as the corresponding factory. This is necessary as the InitializationContext previously exposed {{marshall.core.MarshalledEntry}} and the naming change provides us an easy way to differentiate the context methods as we can't have two getMarshalledEntryFactory methods due to type erasure.
> Due to type erasure it is also necessary to introduce several new methods to the writer/loader methods. Deprecated/Replacement method list below:
> * CacheLoader MarshalledEntry load(Object) -> MarshallableEntry loadEntry(Object)
> * AdvancedCacheLoader Publisher<MarshalledEntry<K, V>> publishEntries(..) -> Publisher<MarshallableEntry<K, V>> entryPublisher(...)
> * CacheWriter writeBatch(Iterable<MarshalledEntry>) -> writeBulk(Publisher)- InitializationContextgetMarshalledEntryFactory->getMarshallableEntryFactory`
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9846) Ensure Backwards Compatibility with Persistence SPI changes
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9846?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9846:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6542
> Ensure Backwards Compatibility with Persistence SPI changes
> -----------------------------------------------------------
>
> Key: ISPN-9846
> URL: https://issues.jboss.org/browse/ISPN-9846
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> ISPN-9693 deprecated the {{org.infinispan.marshall.core.MarshalledEntry}} interface in favour of {{org.infinispan.persistence.spi.MarshalledEntry}}, however this breaks compatibility with 9.4.x stores as the method signatures of the various store/loader interfaces changed.
> Therefore, to aid with enabling backwards compatibility it is necessary to change {{spi.MarshalledEntry}} to {{spi.MarshallableEntry}} as well as the corresponding factory. This is necessary as the InitializationContext previously exposed {{marshall.core.MarshalledEntry}} and the naming change provides us an easy way to differentiate the context methods as we can't have two getMarshalledEntryFactory methods due to type erasure.
> Due to type erasure it is also necessary to introduce several new methods to the writer/loader methods. Deprecated/Replacement method list below:
> * CacheLoader MarshalledEntry load(Object) -> MarshallableEntry loadEntry(Object)
> * AdvancedCacheLoader Publisher<MarshalledEntry<K, V>> publishEntries(..) -> Publisher<MarshallableEntry<K, V>> entryPublisher(...)
> * CacheWriter writeBatch(Iterable<MarshalledEntry>) -> writeBulk(Publisher)- InitializationContextgetMarshalledEntryFactory->getMarshallableEntryFactory`
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9846) Ensure Backwards Compatibility with Persistence SPI changes
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9846?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9846:
-------------------------------
Parent: ISPN-9620
Issue Type: Sub-task (was: Bug)
> Ensure Backwards Compatibility with Persistence SPI changes
> -----------------------------------------------------------
>
> Key: ISPN-9846
> URL: https://issues.jboss.org/browse/ISPN-9846
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> ISPN-9693 deprecated the {{org.infinispan.marshall.core.MarshalledEntry}} interface in favour of {{org.infinispan.persistence.spi.MarshalledEntry}}, however this breaks compatibility with 9.4.x stores as the method signatures of the various store/loader interfaces changed.
> Therefore, to aid with enabling backwards compatibility it is necessary to change {{spi.MarshalledEntry}} to {{spi.MarshallableEntry}} as well as the corresponding factory. This is necessary as the InitializationContext previously exposed {{marshall.core.MarshalledEntry}} and the naming change provides us an easy way to differentiate the context methods as we can't have two getMarshalledEntryFactory methods due to type erasure.
> Due to type erasure it is also necessary to introduce several new methods to the writer/loader methods. Deprecated/Replacement method list below:
> * CacheLoader MarshalledEntry load(Object) -> MarshallableEntry loadEntry(Object)
> * AdvancedCacheLoader Publisher<MarshalledEntry<K, V>> publishEntries(..) -> Publisher<MarshallableEntry<K, V>> entryPublisher(...)
> * CacheWriter writeBatch(Iterable<MarshalledEntry>) -> writeBulk(Publisher)- InitializationContextgetMarshalledEntryFactory->getMarshallableEntryFactory`
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9846) Ensure Backwards Compatibility with Persistence SPI changes
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-9846:
----------------------------------
Summary: Ensure Backwards Compatibility with Persistence SPI changes
Key: ISPN-9846
URL: https://issues.jboss.org/browse/ISPN-9846
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 10.0.0.Alpha2
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Beta1
ISPN-9693 deprecated the {{org.infinispan.marshall.core.MarshalledEntry}} interface in favour of {{org.infinispan.persistence.spi.MarshalledEntry}}, however this breaks compatibility with 9.4.x stores as the method signatures of the various store/loader interfaces changed.
Therefore, to aid with enabling backwards compatibility it is necessary to change {{spi.MarshalledEntry}} to {{spi.MarshallableEntry}} as well as the corresponding factory. This is necessary as the InitializationContext previously exposed {{marshall.core.MarshalledEntry}} and the naming change provides us an easy way to differentiate the context methods as we can't have two getMarshalledEntryFactory methods due to type erasure.
Due to type erasure it is also necessary to introduce several new methods to the writer/loader methods. Deprecated/Replacement method list below:
* CacheLoader MarshalledEntry load(Object) -> MarshallableEntry loadEntry(Object)
* AdvancedCacheLoader Publisher<MarshalledEntry<K, V>> publishEntries(..) -> Publisher<MarshallableEntry<K, V>> entryPublisher(...)
* CacheWriter writeBatch(Iterable<MarshalledEntry>) -> writeBulk(Publisher)- InitializationContextgetMarshalledEntryFactory->getMarshallableEntryFactory`
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9845) Stop exposing InternalMetadata via the persistence SPI
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9845?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9845:
-------------------------------
Parent: ISPN-9620
Issue Type: Sub-task (was: Enhancement)
> Stop exposing InternalMetadata via the persistence SPI
> ------------------------------------------------------
>
> Key: ISPN-9845
> URL: https://issues.jboss.org/browse/ISPN-9845
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> We should stop exposing InternalMetadata via the persistence SPI and add created() methods direct to the MarshallableEntry interface introduced in ISPN-9693. This requires MarshallableEntry to change to:
> {code:java}
> interface MarshallableEntry<K, V> {
> ByteBuffer getKeyBytes();
> ByteBuffer getValueBytes();
> K getKey();
> V getValue();
> Metadata metadata();
> ByteBuffer metadataBytes();
> long created();
> long lastUsed();
> boolean isExpired(long now);
> long expiryTime();
> }
> {code}
> With MarshalledEntry then providing the old method for backwards compatiblity:
> {code:java}
> ByteBuffer getMetadataBytes();
> InternalMetadata getMetadata();
> {code
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9845) Stop exposing InternalMetadata via the persistence SPI
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9845?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9845:
-------------------------------
Description:
We should stop exposing InternalMetadata via the persistence SPI and add created() methods direct to the MarshallableEntry interface introduced in ISPN-9693. This requires MarshallableEntry to change to:
{code:java}
interface MarshallableEntry<K, V> {
ByteBuffer getKeyBytes();
ByteBuffer getValueBytes();
K getKey();
V getValue();
Metadata metadata();
ByteBuffer metadataBytes();
long created();
long lastUsed();
boolean isExpired(long now);
long expiryTime();
}
{code}
With MarshalledEntry then providing the old method for backwards compatiblity:
{code:java}
ByteBuffer getMetadataBytes();
InternalMetadata getMetadata();
{code}
was:
We should stop exposing InternalMetadata via the persistence SPI and add created() methods direct to the MarshallableEntry interface introduced in ISPN-9693. This requires MarshallableEntry to change to:
{code:java}
interface MarshallableEntry<K, V> {
ByteBuffer getKeyBytes();
ByteBuffer getValueBytes();
K getKey();
V getValue();
Metadata metadata();
ByteBuffer metadataBytes();
long created();
long lastUsed();
boolean isExpired(long now);
long expiryTime();
}
{code}
With MarshalledEntry then providing the old method for backwards compatiblity:
{code:java}
ByteBuffer getMetadataBytes();
InternalMetadata getMetadata();
{code
> Stop exposing InternalMetadata via the persistence SPI
> ------------------------------------------------------
>
> Key: ISPN-9845
> URL: https://issues.jboss.org/browse/ISPN-9845
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> We should stop exposing InternalMetadata via the persistence SPI and add created() methods direct to the MarshallableEntry interface introduced in ISPN-9693. This requires MarshallableEntry to change to:
> {code:java}
> interface MarshallableEntry<K, V> {
> ByteBuffer getKeyBytes();
> ByteBuffer getValueBytes();
> K getKey();
> V getValue();
> Metadata metadata();
> ByteBuffer metadataBytes();
> long created();
> long lastUsed();
> boolean isExpired(long now);
> long expiryTime();
> }
> {code}
> With MarshalledEntry then providing the old method for backwards compatiblity:
> {code:java}
> ByteBuffer getMetadataBytes();
> InternalMetadata getMetadata();
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9845) Stop exposing InternalMetadata via the persistence SPI
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-9845:
----------------------------------
Summary: Stop exposing InternalMetadata via the persistence SPI
Key: ISPN-9845
URL: https://issues.jboss.org/browse/ISPN-9845
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Affects Versions: 10.0.0.Alpha2
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Beta1
We should stop exposing InternalMetadata via the persistence SPI and add created() methods direct to the MarshallableEntry interface introduced in ISPN-9693. This requires MarshallableEntry to change to:
{code:java}
interface MarshallableEntry<K, V> {
ByteBuffer getKeyBytes();
ByteBuffer getValueBytes();
K getKey();
V getValue();
Metadata metadata();
ByteBuffer metadataBytes();
long created();
long lastUsed();
boolean isExpired(long now);
long expiryTime();
}
{code}
With MarshalledEntry then providing the old method for backwards compatiblity:
{code:java}
ByteBuffer getMetadataBytes();
InternalMetadata getMetadata();
{code
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-9693.
--------------------------------
Resolution: Done
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Ryan Emerson reopened ISPN-9693:
--------------------------------
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months