[JBoss JIRA] (ISPN-8003) QueryInterceptor and ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck
by Adrian Nistor (Jira)
[ https://issues.jboss.org/browse/ISPN-8003?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-8003:
-------------------------------------
Currently only ProtobufMetadataManagerInterceptor still has this issue. QueryInterceptor was fixed meanwhile.
> QueryInterceptor and ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck
> -----------------------------------------------------------------------------------------------------
>
> Key: ISPN-8003
> URL: https://issues.jboss.org/browse/ISPN-8003
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.2.0.Final, 9.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> {code}
> ProtobufMetadataManagerInterceptor.java:43, InterceptorDefinesAllReadWritesCheck, Priority: Normal
> Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests]
> {code}
> {code}
> QueryInterceptor.java:69, InterceptorDefinesAllReadWritesCheck, Priority: Normal
> Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-9593) Docs: Attributes for OpenShift
by Don Naro (Jira)
Don Naro created ISPN-9593:
------------------------------
Summary: Docs: Attributes for OpenShift
Key: ISPN-9593
URL: https://issues.jboss.org/browse/ISPN-9593
Project: Infinispan
Issue Type: Enhancement
Components: Documentation-Core
Affects Versions: 9.4.1.Final
Reporter: Don Naro
Assignee: Don Naro
Need attributes for OpenShift documentation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-9591) Infinispan BOM
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9591?page=com.atlassian.jira.plugin.... ]
Katia Aresti reassigned ISPN-9591:
----------------------------------
Assignee: Katia Aresti (was: Pedro Ruivo)
> Infinispan BOM
> --------------
>
> Key: ISPN-9591
> URL: https://issues.jboss.org/browse/ISPN-9591
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.0.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> Infinispan 9.4.0.Final bom is including spring-boot as dependency, but we are using spring-boot only in test scope to easily write spring4 and infinispan integration tests
> spring-boot-camel is also added as a dependency
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-9488) Jenkins cleanup script can delete the current build's directory
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9488?page=com.atlassian.jira.plugin.... ]
Diego Lovison closed ISPN-9488.
-------------------------------
> Jenkins cleanup script can delete the current build's directory
> ---------------------------------------------------------------
>
> Key: ISPN-9488
> URL: https://issues.jboss.org/browse/ISPN-9488
> Project: Infinispan
> Issue Type: Bug
> Components: CI
> Affects Versions: 9.4.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_failure
> Fix For: 9.4.0.CR3
>
>
> Our {{Jenkinsfile}} runs {{cleanup.sh}} (provisioned on each agent via Ansible) to make room for the new build. The idea is to keep the checked-out sources after a build, so that the next build for the same branch is faster, and {{cleanup.sh}} only deletes the workspace directories of old builds if there's less than 10gb of free space.
> There is a problem, however: the agent may have less than 10GB of free space after deleting all the old workspace directories, and {{cleanup.sh}} will happily delete the current build's workspace to make more room. Obviously, the build fails afterwards:
> {noformat}
> ERROR: missing workspace /home/infinispan/workspace/Infinispan_PR-6236-6TTBGFU5OA5XZXKEPJRZI245GOIWTNAUH3HC5M6B36G25UNJPTCA on rhos-infinispan-slave-4.localdomain
> {noformat}
> Unfortunately we also use `returnOutput: true` when running the cleanup script, so it's not obvious who is deleting the build directory.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-9488) Jenkins cleanup script can delete the current build's directory
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9488?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9488:
--------------------------------
Tester: Diego Lovison
> Jenkins cleanup script can delete the current build's directory
> ---------------------------------------------------------------
>
> Key: ISPN-9488
> URL: https://issues.jboss.org/browse/ISPN-9488
> Project: Infinispan
> Issue Type: Bug
> Components: CI
> Affects Versions: 9.4.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_failure
> Fix For: 9.4.0.CR3
>
>
> Our {{Jenkinsfile}} runs {{cleanup.sh}} (provisioned on each agent via Ansible) to make room for the new build. The idea is to keep the checked-out sources after a build, so that the next build for the same branch is faster, and {{cleanup.sh}} only deletes the workspace directories of old builds if there's less than 10gb of free space.
> There is a problem, however: the agent may have less than 10GB of free space after deleting all the old workspace directories, and {{cleanup.sh}} will happily delete the current build's workspace to make more room. Obviously, the build fails afterwards:
> {noformat}
> ERROR: missing workspace /home/infinispan/workspace/Infinispan_PR-6236-6TTBGFU5OA5XZXKEPJRZI245GOIWTNAUH3HC5M6B36G25UNJPTCA on rhos-infinispan-slave-4.localdomain
> {noformat}
> Unfortunately we also use `returnOutput: true` when running the cleanup script, so it's not obvious who is deleting the build directory.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-9393) getAsync() and getWithMetadata() does not check NearCache
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-9393?page=com.atlassian.jira.plugin.... ]
Diego Lovison edited comment on ISPN-9393 at 10/8/18 9:14 AM:
--------------------------------------------------------------
I am reopening the issue because the put operation always remove the entry from the near cache
*InvalidatedNearRemoteCache*
{code:java}
public CompletableFuture<V> putAsync(K key, V value, long lifespan, TimeUnit lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) {
if (maxIdleTime > 0L) {
log.nearCacheMaxIdleUnsupported();
}
CompletableFuture<V> ret = super.putAsync(key, value, lifespan, lifespanUnit, maxIdleTime, maxIdleTimeUnit);
return ret.thenApply((v) -> {
this.nearcache.remove(key);
return v;
});
}
{code}
was (Author: dlovison):
I am reopening the issue because the put operation always remote the entry from the near cache
*InvalidatedNearRemoteCache*
{code:java}
public CompletableFuture<V> putAsync(K key, V value, long lifespan, TimeUnit lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) {
if (maxIdleTime > 0L) {
log.nearCacheMaxIdleUnsupported();
}
CompletableFuture<V> ret = super.putAsync(key, value, lifespan, lifespanUnit, maxIdleTime, maxIdleTimeUnit);
return ret.thenApply((v) -> {
this.nearcache.remove(key);
return v;
});
}
{code}
> getAsync() and getWithMetadata() does not check NearCache
> ---------------------------------------------------------
>
> Key: ISPN-9393
> URL: https://issues.jboss.org/browse/ISPN-9393
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, Remote Protocols
> Reporter: Pedro Ruivo
> Assignee: Tristan Tarrant
> Priority: Blocker
> Fix For: 9.4.0.Beta1, 9.4.0.CR3
>
>
> In ISPN-8618, the java client was made async.
> However, the {{getAsync()}} method isn't checking the {{NearCache}} anymore.
> EDIT: {{getWithMetadata()}} isn't check the {{NearCache}}. I'm not sure if it is supposed to check it or not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months