Yes, true…. So, I am looking at a better option for handling the same. Or this should be handled immediately after install process. (install method)
From: Sumit Mohanty [mailto:[email protected]] Sent: 07 July 2015 23:16 To: [email protected]; [email protected] Subject: RE: custom service - client unique_id property I think the id will be regenerated every time the config will be refreshed. That may be an issue. Sent from Outlook<http://taps.io/outlookmobile> On Tue, Jul 7, 2015 at 10:40 AM -0700, "Satyanarayana Jampa" <[email protected]<mailto:[email protected]>> wrote: I am using the template as below: node.properties.j2 node.environment={{node_environment}} node.id={% uuid.uuid4() %} node.data-dir={{node_datadir}} I want to have a unique ID in this property file per each node respectively. Remaiing properties will be populated from the config params defined. Any thoughts on this? From: Sumit Mohanty [mailto:[email protected]] Sent: 07 July 2015 22:24 To: [email protected]<mailto:[email protected]> Subject: Re: custom service - client unique_id property Specifically do you need to add a GUID to the config file - or just using hostname or IP may be enough. Look at ZK stack definition @ https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py It has some logic to create unique ID. ________________________________ From: Satyanarayana Jampa <[email protected]<mailto:[email protected]>> Sent: Tuesday, July 07, 2015 7:44 AM To: [email protected]<mailto:[email protected]> Subject: custom service - client unique_id property Just wondering, if there is a way to generate a unique_id in the property file for each node, for an custom client service. I mean: I have a custom client service component. I am looking for a way to generate a unique_id in the client property file, for each node it gets installed. Thanks, Satya.
