[chef] Re: Re: Node attributes aren't searchable for some reason?

[Ian Marlier < >]

I'll take a look at that setting, Peter.  Thanks for the pointer.  I'll report back once I've got something.

On Tue, May 29, 2012 at 9:15 PM, Peter Donald < " target="_blank"> > wrote:

Hi,

Do the nodes that are not being returned from search have a lot of
attribute data? If so the problem may be that they are failing to be
indexed by solr as you are exceeding the setting maxFieldLength. If
this is the case look for the solr config file on your system and
increase the size of this. (Just be warned the config file actually
appears twice on ubuntu systems for some reason).

HTH

On Wed, May 30, 2012 at 3:00 AM, Ian Marlier < "> > wrote:
> I'm working with the following two nodes, which are supposed to be part of a
> pacemaker cluster:
> chef-repo (hc_production)]$ k node show login01.fal
> --attribute cluster --format json
> {
>   "cluster": {
>     "heartbeat_coredumps": "true",
>     "uuid": "dff82156-9145-4a89-b92a-ba3bb238442b",
>     "udpport": "759",
>     "heartbeat_compression": "bz2",
>     "pacemaker": {
>       "resource_dir": "/usr/lib/ocf/resource.d"
>     },
>     "deadtime": 60,
>     "initdead": 90,
>     "warntime": 30,
>     "keepalive": 5
>   }
> }
> chef-repo (hc_production)]$ k node show login02.fal
> --attribute cluster --format json
> {
>   "cluster": {
>     "heartbeat_coredumps": "true",
>     "uuid": "dff82156-9145-4a89-b92a-ba3bb238442b",
>     "udpport": "759",
>     "heartbeat_compression": "bz2",
>     "deadtime": 60,
>     "pacemaker": {
>       "resource_dir": "/usr/lib/ocf/resource.d"
>     },
>     "initdead": 90,
>     "keepalive": 5,
>     "warntime": 30
>   }
> }
> chef-repo (hc_production)]$
>
>
> However, for reasons that I can't explain, searching based on cluster UUID
> doesn't return these nodes:
>
> chef-repo (hc_production)]$ k search node
> 'cluster_uuid:dff82156-9145-4a89-b92a-ba3bb238442b'
> 0 items found
>
> chef-repo (hc_production)]$
>
>
> Anyone have any idea why this would be?  Is there a way to check the index
> status for a given node or something like that, or to force re-indexing of
> the node?  (Note: I did try editing the node, removing the UUID parameter,
> saving the node, then editing again and adding the UUID parameter back in.)
>
> Thanks,
>
> Ian
>
> --
> Ian Marlier | Senior Systems Engineer
> Brightcove, Inc.
> 290 Congress Street, 4th Floor, Boston, MA 02110
> ">
>

--
Cheers,

Peter Donald

--

Ian Marlier | Senior Systems Engineer

Brightcove, Inc.

290 Congress Street, 4th Floor, Boston, MA 02110
" target="_blank">