> On Jul 21, 2017, at 3:59 AM, Leif Hedstrom wrote:
>
> Hi all,
>
> to avoid further ossification, I’d like to propose the following:
>
> 1. All new configuration files *must* be done using Lua syntax (with the
> appropriate file extension)
I think in the previous thread on file extensions,
+1 to that. thanks!
On Fri, Jul 21, 2017 at 3:59 AM, Leif Hedstrom wrote:
> Hi all,
>
> to avoid further ossification, I’d like to propose the following:
>
> 1. All new configuration files *must* be done using Lua syntax (with the
> appropriate file extension)
>
> 2. For major changes to an exis
Hi all,
to avoid further ossification, I’d like to propose the following:
1. All new configuration files *must* be done using Lua syntax (with the
appropriate file extension)
2. For major changes to an existing configuration file, we *strongly*
recommended to also include a migration to Lua.
> On Jul 21, 2017, at 9:26 AM, Bryan Call wrote:
>
> Can you run sudo perf top -g, do a search (“/“) for spin_lock, and see what
> is calling it?
>
> -Bryan
>
>> On Jul 21, 2017, at 2:51 AM, Phillip Moore wrote:
>>
>>
>> Anyone experience high CPU with 7.1.0 rc1 ? I have it running on 2 no
Can you run sudo perf top -g, do a search (“/“) for spin_lock, and see what is
calling it?
-Bryan
> On Jul 21, 2017, at 2:51 AM, Phillip Moore wrote:
>
>
> Anyone experience high CPU with 7.1.0 rc1 ? I have it running on 2 nodes
> taking production load and it is doing comparable work to oth
Anyone experience high CPU with 7.1.0 rc1 ? I have it running on 2 nodes
taking production load and it is doing comparable work to other 6.2.1 nodes
in both cases. in one case the CPU climbed to 100% of all 32 cores and
stayed stuck there, in the other one the CPU is in line with other nodes.
I'm n
