couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randall Leeds <randall.le...@gmail.com>
Subject Re: accidentally used same uuid on multiple servers
Date Wed, 12 Jun 2013 17:28:22 GMT
Is there something we could do with some hardware info (MAC addresses,
disk UUIDs, etc) to notice when the UUID might not have been generated
on this hardware and log a warning? Would that even be helpful?

On Wed, Jun 12, 2013 at 7:04 AM, Robert Newson <rnewson@apache.org> wrote:
> Sure, you can do that, the trick here is knowing you need to (and,
> conversely, knowing you shouldn't copy a local.ini if couchdb has
> added a uuid property).
>
> B.
>
>
> On 12 June 2013 14:56, Alexander Shorin <kxepal@gmail.com> wrote:
>> On Thu, May 2, 2013 at 7:24 PM, Ian Ward <ianshward@gmail.com> wrote:
>>> rnewson asked me to write to the list about the above, in order to
>>> discuss storing uuid in a place where it may be less likely to be
>>> copied in deployment management systems / scripts like Puppet.
>>
>> It is possible to create custom ini file within %localconfdir%/local.d
>> (/etc/couchdb/local.d for instance) directory which will override
>> local.ini uuid option:
>>
>> [couchdb]
>> uuid = myuuid
>>
>> This file may be automatically generated with puppet without need to
>> edit local.ini on each instance.
>>
>> --
>> ,,,^..^,,,

Mime
View raw message