[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-12868:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: HFDS-7240
Status: Resolved (was: Patch Available)
Thanks [~nandakumar131] for the contribution. I've committed the patch to the
feature branch.
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>Priority: Major
> Fix For: HFDS-7240
>
> Attachments: HDFS-12868-HDFS-7240.000.patch,
> HDFS-12868-HDFS-7240.001.patch, HDFS-12868-HDFS-7240.002.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Attachment: HDFS-12868-HDFS-7240.002.patch
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>Priority: Major
> Attachments: HDFS-12868-HDFS-7240.000.patch,
> HDFS-12868-HDFS-7240.001.patch, HDFS-12868-HDFS-7240.002.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Attachment: HDFS-12868-HDFS-7240.001.patch
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>Priority: Major
> Attachments: HDFS-12868-HDFS-7240.000.patch,
> HDFS-12868-HDFS-7240.001.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Status: Open (was: Patch Available)
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
> Attachments: HDFS-12868-HDFS-7240.000.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Status: Patch Available (was: Open)
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
> Attachments: HDFS-12868-HDFS-7240.000.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Attachment: HDFS-12868-HDFS-7240.000.patch
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
> Attachments: HDFS-12868-HDFS-7240.000.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Status: Patch Available (was: In Progress)
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
> Attachments: HDFS-12868-HDFS-7240.000.patch
>
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Description:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
was:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM. The client should first connect to KSM and get
all the required configurations.
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Description:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM. The client should first connect to KSM and get
all the required configurations.
was:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM. The client should first connect to KSM and get
> all the required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDFS-12868:
---
Description:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
was:
qCurrently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>
> Currently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12868) Ozone: Service Discovery API
[
https://issues.apache.org/jira/browse/HDFS-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDFS-12868:
Description:
qCurrently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
was:
Currently if a client wants to connect to Ozone cluster we need multiple
properties to be configured in the client.
For RPC based connection we need
{{ozone.ksm.address}}
{{ozone.scm.client.address}}
and the ports if something other than default is configured.
For REST based connection
{{ozone.rest.servers}}
and port if something other than default is configured.
With the introduction of Service Discovery API the client should be able to
discover all the configurations needed for the connection. Service discovery
calls will be handled by KSM, at the client side, we only need to configure
{{ozone.ksm.address}}. The client should first connect to KSM and get all the
required configurations.
> Ozone: Service Discovery API
>
>
> Key: HDFS-12868
> URL: https://issues.apache.org/jira/browse/HDFS-12868
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Nanda kumar
>Assignee: Nanda kumar
>
> qCurrently if a client wants to connect to Ozone cluster we need multiple
> properties to be configured in the client.
> For RPC based connection we need
> {{ozone.ksm.address}}
> {{ozone.scm.client.address}}
> and the ports if something other than default is configured.
> For REST based connection
> {{ozone.rest.servers}}
> and port if something other than default is configured.
> With the introduction of Service Discovery API the client should be able to
> discover all the configurations needed for the connection. Service discovery
> calls will be handled by KSM, at the client side, we only need to configure
> {{ozone.ksm.address}}. The client should first connect to KSM and get all the
> required configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
