Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

zookeeper_cluster (3) Versions 3.0.4

Zookeeper, a distributed high-availability consistent datastore

Berkshelf/Librarian
Policyfile
Knife
cookbook 'zookeeper_cluster', '~> 3.0.4'
cookbook 'zookeeper_cluster', '~> 3.0.4', :supermarket
knife cookbook site install zookeeper_cluster
knife cookbook site download zookeeper_cluster
README
Dependencies
Quality 44%

zookeeper chef cookbook

Zookeeper, a distributed high-availability consistent datastore

Overview

This cookbook installs zookeeper from the Cloudera apt repo.

The server recipe additionally * creates the service, and applies the state given in node[:zookeeper][:server][:daemon_state] * announces zookeeper-server

Recipes

  • client - Installs Zookeeper client libraries
  • config_files - Config files -- include this last after discovery
  • default - Base configuration for zookeeper
  • server - Installs Zookeeper server, sets up and starts service

Integration

Supports platforms: debian and ubuntu

Cookbook dependencies: * java * apt * runit * volumes * metachef * hadoop_cluster

Attributes

  • [:groups][:zookeeper][:gid] - (default: "305")
  • [:zookeeper][:data_dir] - (default: "/var/zookeeper")
    • [set by recipe]
  • [:zookeeper][:journal_dir] - (default: "/var/zookeeper")
    • [set by recipe]
  • [:zookeeper][:cluster_name] - (default: "cluster_name")
  • [:zookeeper][:log_dir] - (default: "/var/log/zookeeper")
  • [:zookeeper][:max_client_connections] - (default: "300")
    • Limits the number of concurrent connections (at the socket level) that a single client, identified by IP address, may make to a single member of the ZooKeeper ensemble. This is used to prevent certain classes of DoS attacks, including file descriptor exhaustion. The zookeeper default is 60; this file bumps that to 300, but you will want to turn this up even more on a production machine. Setting this to 0 entirely removes the limit on concurrent connections.
  • [:zookeeper][:home_dir] - (default: "/usr/lib/zookeeper")
  • [:zookeeper][:exported_jars] -
  • [:zookeeper][:conf_dir] - (default: "/etc/zookeeper")
  • [:zookeeper][:user] - (default: "zookeeper")
  • [:zookeeper][:pid_dir] - (default: "/var/run/zookeeper")
  • [:zookeeper][:client_port] - (default: "2181")
  • [:zookeeper][:jmx_dash_port] - (default: "2182")
  • [:zookeeper][:leader_port] - (default: "2888")
  • [:zookeeper][:election_port] - (default: "3888")
  • [:zookeeper][:java_heap_size_max] - (default: "1000")
  • [:zookeeper][:tick_time] - (default: "2000")
    • the length of a single tick, which is the basic time unit used by ZooKeeper, as measured in milliseconds. It is used to regulate heartbeats, and timeouts. For example, the minimum session timeout will be two ticks.
  • [:zookeeper][:snapshot_trigger] - (default: "100000")
    • ZooKeeper logs transactions to a transaction log. After snapCount transactions are written to a log file a snapshot is started and a new transaction log file is created. The default snapCount is 100,000.
  • [:zookeeper][:initial_timeout_ticks] - (default: "10")
    • Time, in ticks, to allow followers to connect and sync to a leader. Increase if the amount of data managed by ZooKeeper is large
  • [:zookeeper][:sync_timeout_ticks] - (default: "5")
    • Time, in ticks, to allow followers to sync with ZooKeeper. If followers fall too far behind a leader, they will be dropped.
  • [:zookeeper][:leader_is_also_server] - (default: "auto")
    • Should the leader accepts client connections? default "yes". The leader machine coordinates updates. For higher update throughput at thes slight expense of read throughput the leader can be configured to not accept clients and focus on coordination. The default to this option is yes, which means that a leader will accept client connections. Turning on leader selection is highly recommended when you have more than three ZooKeeper servers in an ensemble. "auto" means "true if there are 4 or more zookeepers, false otherwise"
  • [:zookeeper][:server][:run_state] - (default: "stop")
  • [:users][:zookeeper][:uid] - (default: "305")

License and Author

Author:: Chris Howe - Infochimps, Inc (coders@infochimps.com) Copyright:: 2011, Chris Howe - Infochimps, Inc

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

readme generated by cluster_chef's cookbook_munger

Dependent cookbooks

hadoop_cluster >= 0.0.0
metachef >= 0.0.0
volumes >= 0.0.0
runit >= 0.0.0
apt >= 0.0.0
java >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

3.0.4 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

3.0.4 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

3.0.4 failed this metric

FC007: Ensure recipe dependencies are reflected in cookbook metadata: zookeeper_cluster/recipes/client.rb:22
FC007: Ensure recipe dependencies are reflected in cookbook metadata: zookeeper_cluster/recipes/client.rb:27
FC007: Ensure recipe dependencies are reflected in cookbook metadata: zookeeper_cluster/recipes/server.rb:24
FC007: Ensure recipe dependencies are reflected in cookbook metadata: zookeeper_cluster/recipes/server.rb:72
FC047: Attribute assignment does not specify precedence: zookeeper_cluster/recipes/client.rb:25
FC047: Attribute assignment does not specify precedence: zookeeper_cluster/recipes/config_files.rb:37
FC047: Attribute assignment does not specify precedence: zookeeper_cluster/recipes/server.rb:61
FC064: Ensure issues_url is set in metadata: zookeeper_cluster/metadata.rb:1
FC065: Ensure source_url is set in metadata: zookeeper_cluster/metadata.rb:1
FC066: Ensure chef_version is set in metadata: zookeeper_cluster/metadata.rb:1
FC069: Ensure standardized license defined in metadata: zookeeper_cluster/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: zookeeper_cluster/metadata.rb:1
Run with Foodcritic Version 12.2.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

3.0.4 passed this metric

No Binaries Metric
            

3.0.4 passed this metric

Publish Metric
            

3.0.4 passed this metric

Supported Platforms Metric
            

3.0.4 passed this metric

Testing File Metric
            

3.0.4 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

3.0.4 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number