[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-9498?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-9498:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Index filesystem paths in server should point to data directory
> ---------------------------------------------------------------
>
> Key: ISPN-9498
> URL: https://issues.redhat.com/browse/ISPN-9498
> Project: Infinispan
> Issue Type: Bug
> Components: Indexing, OpenShift, Server
> Affects Versions: 9.4.0.CR1, 9.3.3.Final
> Reporter: Galder Zamarreño
> Assignee: Tristan Tarrant
> Priority: Major
>
> Certain indexing configurations result in using filesystem as index storage.
> When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data.
> When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts.
> Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...].
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10532) org.antlr.runtime.RecognitionException class leaks from logger interface of object-filter
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10532?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10532:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> org.antlr.runtime.RecognitionException class leaks from logger interface of object-filter
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-10532
> URL: https://issues.redhat.com/browse/ISPN-10532
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.16.Final, 10.0.0.CR1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.CR2, 9.4.17.Final
>
>
> This prevents ANTLR to be actually shaded. The effect of the shade plugin is quasi-no-op. The dependency is still carried around and hacks have been done to cope with it https://github.com/infinispan/infinispan/blob/10.0.0.CR1/feature-pack/emb...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-7889) BaseDistributionInterceptor.remoteGet may cause concurrency issues
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-7889?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-7889:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> BaseDistributionInterceptor.remoteGet may cause concurrency issues
> ------------------------------------------------------------------
>
> Key: ISPN-7889
> URL: https://issues.redhat.com/browse/ISPN-7889
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.1.0.Alpha1
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Alpha3, 9.4.6.Final
>
>
> {{BaseDistributionInterceptor.remoteGet}} or any call that accesses the context in an async future handler that is called multiple times in parallel may lead to concurrent modifications of the context.
> These calls are usually handled using {{CompletableFuture.allOf()}} or using a CF with counter, but if one of the calls results in exceptional completion of the composed future, the processing continues (e.g. with a retry). The other parallel operation handlers are not stopped, though.
> {{BaseDistributionInterceptor.remoteGet}} shouldn't be called in parallel because it does not even synchronize regular successful invocations.
> A problem like this caused failures in {{GetAllCommandStressTest}}, and the issue was addressed for {{GetAllCommand}} in ISPN-7884.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10376) Optimize operation to get keys from a cache
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10376?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10376:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Optimize operation to get keys from a cache
> -------------------------------------------
>
> Key: ISPN-10376
> URL: https://issues.redhat.com/browse/ISPN-10376
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 10.0.0.CR2
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> The REST v1 API allocates all the keys at once in memory and sends them, and REST v2 currently is not offering this operation
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10552) Ignored caches should be per server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10552?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10552:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Ignored caches should be per server
> -----------------------------------
>
> Key: ISPN-10552
> URL: https://issues.redhat.com/browse/ISPN-10552
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: console-ng, rest
> Fix For: 10.0.0.CR3
>
>
> The new server has ignored caches as a configuration for each endopoint, it should not be a configuration but a runtime persisted state that affects all the cluster
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10580) Cluster resource
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10580?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10580:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Cluster resource
> ----------------
>
> Key: ISPN-10580
> URL: https://issues.redhat.com/browse/ISPN-10580
> Project: Infinispan
> Issue Type: Feature Request
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Katia Aresti
> Priority: Major
> Labels: console-ng
>
> A resource to expose cluster-wide info and operations:
> * Shutdown the whole cluster
> * Health of all cache managers from the server
> * List of nodes
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10571) CORS usability issues
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10571?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10571:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> CORS usability issues
> ---------------------
>
> Key: ISPN-10571
> URL: https://issues.redhat.com/browse/ISPN-10571
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: console-ng
> Fix For: 10.0.0.CR2
>
>
> * OPTIONS is currently only handled by CORS for the pre-flight. Regular OPTIONS requests throw an error.
> * By default, localhost is not allowed
> * Specifying origin with '*' (all origins allowed) is not working
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-10435) Support for serving static content
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10435?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10435:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Support for serving static content
> ----------------------------------
>
> Key: ISPN-10435
> URL: https://issues.redhat.com/browse/ISPN-10435
> Project: Infinispan
> Issue Type: Feature Request
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: console-ng
> Fix For: 10.0.0.CR2
>
>
> The REST endpoint should be able to serve the console from a static folder, respecting usual http headers sent by browsers to facilitate caching such as if-modified-since
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (ISPN-9847) Extend configuration to allow inline JGroups configuration and inheritance
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-9847?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-9847:
-----------------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Extend configuration to allow inline JGroups configuration and inheritance
> --------------------------------------------------------------------------
>
> Key: ISPN-9847
> URL: https://issues.redhat.com/browse/ISPN-9847
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 10.0.0.Alpha2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta1, 10.0.0.Final
>
>
> 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.13.8#713008)
4 years, 12 months