[JBoss JIRA] (WFLY-11750) Allow cluster to use DNS addresses instead of IP addresses
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin... ]
Tomasz Adamski edited comment on WFLY-11750 at 2/25/19 3:32 PM:
----------------------------------------------------------------
[~pferraro] But if I understand correctly HA features and correct transaction recovery are independent.
Let's suppose we are on bare-metal and have a cluster of n nodes.
At some point, one of the nodes is invoked by the client, takes part in the transaction with two-phase commit and after prepare stage the node fails.
As a result, the client has a record in its permanent object store and tries to finish the transaction. As the record contains the IP address of the failed node the client will wait till the server is up again to finish the transaction.
That node will have the new cluster identity. My understanding is that it has no effect on transaction recovery which will work fine.
On the other hand, OpenShift does not guarantee the IP node identity - only DNS identity - so IMO the cluster will work fine but recovery won't.
But the key thing here IMO is, the way remoting gets node information. When clustering is involved it gets raw IP addresses which won't work fine on OpenShift and my thought was that the simplest solution would be to use DNS addresses as base for cluster operation.
was (Author: tomekadamski):
[~pferraro] But if I understand correctly HA features and correct transaction recovery are independent.
Let's suppose we are on bare-metal and have a cluster of n nodes.
At some point, one of the nodes (let's call it node A) is invoked by the client, takes part in the transaction with two-phase commit and after prepare stage the node fails.
As a result, the client has a record in its permanent object store and tries to finish the transaction. As the record contains the IP address of the failed node the client will wait till the server is up again to finish the transaction.
That node will have the new cluster identity. My understanding is that it has no effect on transaction recovery which will work fine.
On the other hand, OpenShift does not guarantee the IP node identity - only DNS identity - so IMO the cluster will work fine but recovery won't.
But the key thing here IMO is, the way remoting gets node information. When clustering is involved it gets raw IP addresses which won't work fine on OpenShift and my thought was that the simplest solution would be to use DNS addresses as base for cluster operation.
> Allow cluster to use DNS addresses instead of IP addresses
> ----------------------------------------------------------
>
> Key: WFLY-11750
> URL: https://issues.jboss.org/browse/WFLY-11750
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Paul Ferraro
> Priority: Major
>
> We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.
> Sample scenario that may currently fail when application are deployed in OpenShift:
> A (application)
> B (clustered application)
> 1. A calls transactional invocation on B
> 2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
> 3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
> 4. B node fails
> 5. OpenShift restarts node B on another IP address
> 6. A attempts recovery and persistently fails
> OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11750) Allow cluster to use DNS addresses instead of IP addresses
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin... ]
Tomasz Adamski commented on WFLY-11750:
---------------------------------------
[~pferraro] But if I understand correctly HA features and correct transaction recovery are independent.
Let's suppose we are on bare-metal and have a cluster of n nodes.
At some point, one of the nodes (let's call it node A) is invoked by the client, takes part in the transaction with two-phase commit and after prepare stage the node fails.
As a result, the client has a record in its permanent object store and tries to finish the transaction. As the record contains the IP address of the failed node the client will wait till the server is up again to finish the transaction.
That node will have the new cluster identity. My understanding is that it has no effect on transaction recovery which will work fine.
On the other hand, OpenShift does not guarantee the IP node identity - only DNS identity - so IMO the cluster will work fine but recovery won't.
But the key thing here IMO is, the way remoting gets node information. When clustering is involved it gets raw IP addresses which won't work fine on OpenShift and my thought was that the simplest solution would be to use DNS addresses as base for cluster operation.
> Allow cluster to use DNS addresses instead of IP addresses
> ----------------------------------------------------------
>
> Key: WFLY-11750
> URL: https://issues.jboss.org/browse/WFLY-11750
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Paul Ferraro
> Priority: Major
>
> We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.
> Sample scenario that may currently fail when application are deployed in OpenShift:
> A (application)
> B (clustered application)
> 1. A calls transactional invocation on B
> 2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
> 3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
> 4. B node fails
> 5. OpenShift restarts node B on another IP address
> 6. A attempts recovery and persistently fails
> OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3704) [DMN Designer] Boxed expressions - Decision Table - Input clause - Properties panel is not consistent
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3704?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3704:
--------------------------------------------
[~uxdlc] IIUC we need to keep the panel consistent with the Decision Table - where _consistent_ means that the panel must show the same values we see in the table.
Regarding the interaction in the panel, since it's something for advanced users, we won't spend much time improving the interaction there (just keeping the input values synchronized is enough).
Am I missing something, [~tirelli]?
> [DMN Designer] Boxed expressions - Decision Table - Input clause - Properties panel is not consistent
> -----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3704
> URL: https://issues.jboss.org/browse/DROOLS-3704
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: 1.png
>
>
> Properties panel is not consistent with the popover:
> !1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3706:
-------------------------------------
[~karreiro] posting a mockup here, thank you !Screen Shot 2019-02-25 at 2.33.44 PM.png|thumbnail!
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3706:
--------------------------------
Attachment: Screen Shot 2019-02-25 at 2.33.44 PM.png
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-02-25 at 2.33.44 PM.png
>
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11750) Allow cluster to use DNS addresses instead of IP addresses
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-11750:
-------------------------------------
[~tomekadamski] This is a general issue with any client connecting to a cluster containing a single member. Once that node is restarted, by design, it has a new cluster identity. It doesn't matter whether the same instance is restarted with a new IP address, or with the same IP address, the cluster identity will be different. Thus, recording client mappings using DNS names instead of network addresses does not circumvent the issue. This means that a cluster must contain multiple members in order to provide true HA behavior to the client.
> Allow cluster to use DNS addresses instead of IP addresses
> ----------------------------------------------------------
>
> Key: WFLY-11750
> URL: https://issues.jboss.org/browse/WFLY-11750
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Paul Ferraro
> Priority: Major
>
> We would need a configuration that would allow for the cluster to use DNS addresses instead of IP addresses. The reason is that OpenShift guarantees the node identity under DNS address and not under IP address.
> Sample scenario that may currently fail when application are deployed in OpenShift:
> A (application)
> B (clustered application)
> 1. A calls transactional invocation on B
> 2. as a result of discovery process A obtains a cluster topology from B and uses one of obtained IP addresses for the connection
> 3. as the invocation is transactional the object-store records are written in A's persistent object store; those records are based on the data obtained from the cluster => subordinate node is identified by the IP address from point two
> 4. B node fails
> 5. OpenShift restarts node B on another IP address
> 6. A attempts recovery and persistently fails
> OTOH OpenShift guarantees node identity under DNS address. As a result, at point 5 node is guaranteed to restart on established DNS address so if the cluster used this address instead of physical addresses the scenario above will finish with A being able to recover the transaction.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3703) [DMN Designer] Data Types - Constraints - Disable Enumeration/Range components for Any and disable constraints for Context
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3703?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3703:
---------------------------------------
Description:
Disable Enumeration and Range components for Any/Context types.
See (type vs. constraint dropdown):
{{*Any* - Expression}} ⚠️
{{*boolean* - Disabled}}
{{*context* - Disabled}} ⚠️
{{*date* - Expression, Enumeration, Range}}
{{*date and time* - Expression, Enumeration, Range}}
{{*days and time duration* - Expression, Enumeration, Range}}
{{*number* - Expression, Enumeration, Range}}
{{*string* - Expression, Enumeration, Range}}
{{*time* - Expression, Enumeration, Range}}
{{*years and months duration* - Expression, Enumeration, Range}}
{{*Structure* - Disabled}}
was:
Disable Enumeration and Range components for Any/Context types.
See (type vs. constraint dropdown):
{{*Any* - Expression}}
{{*boolean* - Disabled}}
{{*context* - Expression}}
{{*date* - Expression, Enumeration, Range}}
{{*date and time* - Expression, Enumeration, Range}}
{{*days and time duration* - Expression, Enumeration, Range}}
{{*number* - Expression, Enumeration, Range}}
{{*string* - Expression, Enumeration, Range}}
{{*time* - Expression, Enumeration, Range}}
{{*years and months duration* - Expression, Enumeration, Range}}
{{*Structure* - Disabled}}
> [DMN Designer] Data Types - Constraints - Disable Enumeration/Range components for Any and disable constraints for Context
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3703
> URL: https://issues.jboss.org/browse/DROOLS-3703
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Disable Enumeration and Range components for Any/Context types.
> See (type vs. constraint dropdown):
> {{*Any* - Expression}} ⚠️
> {{*boolean* - Disabled}}
> {{*context* - Disabled}} ⚠️
> {{*date* - Expression, Enumeration, Range}}
> {{*date and time* - Expression, Enumeration, Range}}
> {{*days and time duration* - Expression, Enumeration, Range}}
> {{*number* - Expression, Enumeration, Range}}
> {{*string* - Expression, Enumeration, Range}}
> {{*time* - Expression, Enumeration, Range}}
> {{*years and months duration* - Expression, Enumeration, Range}}
> {{*Structure* - Disabled}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3703) [DMN Designer] Data Types - Constraints - Disable Enumeration/Range components for Any and disable constraints for Context
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3703?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3703:
---------------------------------------
Summary: [DMN Designer] Data Types - Constraints - Disable Enumeration/Range components for Any and disable constraints for Context (was: [DMN Designer] Data Types - Constraints - Disable Enumeration and Range components for Any/Context types)
> [DMN Designer] Data Types - Constraints - Disable Enumeration/Range components for Any and disable constraints for Context
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3703
> URL: https://issues.jboss.org/browse/DROOLS-3703
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Disable Enumeration and Range components for Any/Context types.
> See (type vs. constraint dropdown):
> {{*Any* - Expression}}
> {{*boolean* - Disabled}}
> {{*context* - Expression}}
> {{*date* - Expression, Enumeration, Range}}
> {{*date and time* - Expression, Enumeration, Range}}
> {{*days and time duration* - Expression, Enumeration, Range}}
> {{*number* - Expression, Enumeration, Range}}
> {{*string* - Expression, Enumeration, Range}}
> {{*time* - Expression, Enumeration, Range}}
> {{*years and months duration* - Expression, Enumeration, Range}}
> {{*Structure* - Disabled}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months