[ https://issues.jboss.org/browse/ISPN-5807?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-5807:
--------------------------------------
Status: Open (was: New)
> Display expected nodes mismatch
> -------------------------------
>
> Key: ISPN-5807
> URL: https://issues.jboss.org/browse/ISPN-5807
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
>
> As an administrator, I want to ensure that number of nodes in the physical cluster matches the number of nodes expected on the Management console. I want to see a warning if this is not the case.
> A warning message will be displayed, as shown at:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cluster-no...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6513?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-6513:
--------------------------------
Status: Open (was: New)
> Inconsistencies in Maven pom files
> ----------------------------------
>
> Key: ISPN-6513
> URL: https://issues.jboss.org/browse/ISPN-6513
> Project: Infinispan
> Issue Type: Task
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Gencur
> Assignee: Martin Gencur
> Priority: Minor
> Attachments: wolf_validator_results.txt
>
>
> The output of Wolf validator is attached. It reveals some bad practices and flaws in Maven pom files within the project. Let's address the most important ones.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6513?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-6513:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4251
> Inconsistencies in Maven pom files
> ----------------------------------
>
> Key: ISPN-6513
> URL: https://issues.jboss.org/browse/ISPN-6513
> Project: Infinispan
> Issue Type: Task
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Gencur
> Assignee: Martin Gencur
> Priority: Minor
> Attachments: wolf_validator_results.txt
>
>
> The output of Wolf validator is attached. It reveals some bad practices and flaws in Maven pom files within the project. Let's address the most important ones.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6514?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6514:
--------------------------------
Status: Open (was: New)
> Reduce netty write allocation by using voidPromise when not waiting for completion
> ----------------------------------------------------------------------------------
>
> Key: ISPN-6514
> URL: https://issues.jboss.org/browse/ISPN-6514
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.0.0.Alpha2
>
>
> When a netty write or write and flush is performed and we don't use the future, we should be passing a void promise to avoid allocating those objects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6514?page=com.atlassian.jira.plugin.... ]
Work on ISPN-6514 started by William Burns.
-------------------------------------------
> Reduce netty write allocation by using voidPromise when not waiting for completion
> ----------------------------------------------------------------------------------
>
> Key: ISPN-6514
> URL: https://issues.jboss.org/browse/ISPN-6514
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.0.0.Alpha2
>
>
> When a netty write or write and flush is performed and we don't use the future, we should be passing a void promise to avoid allocating those objects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
William Burns created ISPN-6514:
-----------------------------------
Summary: Reduce netty write allocation by using voidPromise when not waiting for completion
Key: ISPN-6514
URL: https://issues.jboss.org/browse/ISPN-6514
Project: Infinispan
Issue Type: Bug
Components: Server
Reporter: William Burns
Assignee: William Burns
Fix For: 9.0.0.Alpha2
When a netty write or write and flush is performed and we don't use the future, we should be passing a void promise to avoid allocating those objects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6472?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-6472:
-----------------------------------
Fix Version/s: 9.0.0.Alpha2
> Add EXTERNAL SASL support to the server
> ---------------------------------------
>
> Key: ISPN-6472
> URL: https://issues.jboss.org/browse/ISPN-6472
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols, Security, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Alpha2, 9.0.0.Final
>
>
> The server should be able to support the SASL EXTERNAL mech.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-6472?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-6472:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Add EXTERNAL SASL support to the server
> ---------------------------------------
>
> Key: ISPN-6472
> URL: https://issues.jboss.org/browse/ISPN-6472
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols, Security, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Final
>
>
> The server should be able to support the SASL EXTERNAL mech.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)