DataStax Support Forums » Topic: There was a problem with the Cassandra Hive MetaStore

DataStax Support Forums » Topic: There was a problem with the Cassandra Hive MetaStore http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore Software, Support, and Training for Apache Cassandra en-US Sat, 25 May 2013 17:12:22 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php Yewei on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-123 Thu, 26 May 2011 17:22:51 +0000 Yewei 123@http://www.datastax.com/support-forums/ Glad that you got it work. Let us know if you need any further help. Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-121 Thu, 26 May 2011 15:45:04 +0000 Prosperent 121@http://www.datastax.com/support-forums/ Got it working by adding a second hostname entry to the hosts file for the private lan. Somewhere mapreduce internally uses the hostname for the connections, and since our hostname was bound to our public ip, it wasn't able to route through the private lan. So, if anyone has dual nic's with a private and public lan, there is your solution. Thank you guys for the tips and help :) Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-114 Wed, 25 May 2011 20:42:21 +0000 Prosperent 114@http://www.datastax.com/support-forums/ I think the issue is that it is using the hostname for some reason, but the cassandra servers communicate over our private lan. Nothing else seems to have a problem figuring that out, but the reduce portion of map reduce is using the host name instead of our 10.17.91.xxx private lan addresses that are configured everywhere. Even doing a hostname -f at the command line gives me the proper FQDN that resolves to our server, but it resolves to our public network, not the private lan that cassandra is configured to communicate across. Does that make sense? tjake on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-112 Wed, 25 May 2011 19:08:43 +0000 tjake 112@http://www.datastax.com/support-forums/ Looks like there is somthing wrong with your DNS: java.net.UnknownHostException: cass02 Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-107 Wed, 25 May 2011 15:17:16 +0000 Prosperent 107@http://www.datastax.com/support-forums/ To answer the other questions asked above, running : nodetool -h 10.17.91.132 ring returns the expected data: 10.17.91.132 Up Normal 118.84 MB 33.33% 0 10.17.91.140 Up Normal 119.3 MB 33.33% 56713727820156410577229101238628035242 10.17.91.138 Up Normal 116.8 MB 33.33% 113427455640312821154458202477256070485 I run brisk hive simply as: brisk hive -f demos/portfolio_manager/10_day_loss.q Which runs the map process with no issues, but fails when it hits reduce. Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-106 Wed, 25 May 2011 14:19:32 +0000 Prosperent 106@http://www.datastax.com/support-forums/ Still getting the issue with map running and completing, but reduce fails with connection issues: 2011-05-25 09:11:33,879 Stage-1 map = 0%, reduce = 0% 2011-05-25 09:11:39,990 Stage-1 map = 33%, reduce = 0% 2011-05-25 09:11:41,041 Stage-1 map = 67%, reduce = 0% 2011-05-25 09:11:45,105 Stage-1 map = 100%, reduce = 0% 2011-05-25 09:11:49,128 Stage-1 map = 100%, reduce = 11% 2011-05-25 09:11:58,177 Stage-1 map = 100%, reduce = 0% 2011-05-25 09:12:11,264 Stage-1 map = 100%, reduce = 11% 2011-05-25 09:12:14,280 Stage-1 map = 100%, reduce = 0% 2011-05-25 09:12:27,363 Stage-1 map = 100%, reduce = 11% 2011-05-25 09:12:30,391 Stage-1 map = 100%, reduce = 0% 2011-05-25 09:12:42,496 Stage-1 map = 100%, reduce = 11% 2011-05-25 09:12:45,512 Stage-1 map = 100%, reduce = 0% 2011-05-25 09:12:50,586 Stage-1 map = 100%, reduce = 100% Ended Job = job_201105241523_0004 with errors FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask root@cass01:/usr/share/brisk-demos/portfolio_manager# We have 3 brisk nodes connected by a private lan on a 10.17.91.xxx subnet. We've been running these for over a year now, so there are no communication problems between the nodes. It appears from the hadoop logs that it is trying to connect to the nodes by a partial hostname. I see cass01, cass02, and cass03 which is the first part of our host name for each server with the domain cut off. We don't have that configured anywhere in our cassandra config.yaml. here is our config file: # Cassandra storage config YAML # NOTE: # See <a href="http://wiki.apache.org/cassandra/StorageConfiguration" rel="nofollow">http://wiki.apache.org/cassandra/StorageConfiguration</a> for # full explanations of configuration directives # /NOTE # The name of the cluster. This is mainly used to prevent machines in # one logical cluster from joining another. cluster_name: 'Prosperent' # You should always specify InitialToken when setting up a production # cluster for the first time, and often when adding capacity later. # The principle is that each node should be given an equal slice of # the token ring; see <a href="http://wiki.apache.org/cassandra/Operations" rel="nofollow">http://wiki.apache.org/cassandra/Operations</a> # for more details. # # If blank, Cassandra will request a token bisecting the range of # the heaviest-loaded existing node. If there is no load information # available, such as is the case with a new cluster, it will pick # a random token, which will lead to hot spots. initial_token: 0 # Set to true to make new [non-seed] nodes automatically migrate data # to themselves from the pre-existing nodes in the cluster. Defaults # to false because you can only bootstrap N machines at a time from # an existing cluster of N, so if you are bringing up a cluster of # 10 machines with 3 seeds you would have to do it in stages. Leaving # this off for the initial start simplifies that. auto_bootstrap: false # See <a href="http://wiki.apache.org/cassandra/HintedHandoff" rel="nofollow">http://wiki.apache.org/cassandra/HintedHandoff</a> hinted_handoff_enabled: true # this defines the maximum amount of time a dead host will have hints # generated. After it has been dead this long, hints will be dropped. max_hint_window_in_ms: 3600000 # one hour # Sleep this long after delivering each row or row fragment hinted_handoff_throttle_delay_in_ms: 50 # authentication backend, implementing IAuthenticator; used to identify users authenticator: org.apache.cassandra.auth.AllowAllAuthenticator # authorization backend, implementing IAuthority; used to limit access/provide permissions authority: org.apache.cassandra.auth.AllowAllAuthority # The partitioner is responsible for distributing rows (by key) across # nodes in the cluster. Any IPartitioner may be used, including your # own as long as it is on the classpath. Out of the box, Cassandra # provides org.apache.cassandra.dht.RandomPartitioner # org.apache.cassandra.dht.ByteOrderedPartitioner, # org.apache.cassandra.dht.OrderPreservingPartitioner (deprecated), # and org.apache.cassandra.dht.CollatingOrderPreservingPartitioner # (deprecated). # # - RandomPartitioner distributes rows across the cluster evenly by md5. # When in doubt, this is the best option. # - ByteOrderedPartitioner orders rows lexically by key bytes. BOP allows # scanning rows in key order, but the ordering can generate hot spots # for sequential insertion workloads. # - OrderPreservingPartitioner is an obsolete form of BOP, that stores # - keys in a less-efficient format and only works with keys that are # UTF8-encoded Strings. # - CollatingOPP colates according to EN,US rules rather than lexical byte # ordering. Use this as an example if you need custom collation. # # See <a href="http://wiki.apache.org/cassandra/Operations" rel="nofollow">http://wiki.apache.org/cassandra/Operations</a> for more on # partitioners and token selection. partitioner: org.apache.cassandra.dht.RandomPartitioner # directories where Cassandra should store data on disk. data_file_directories: - /data # commit log commitlog_directory: /var/lib/cassandra/commitlog # saved caches saved_caches_directory: /data/saved_caches # Size to allow commitlog to grow to before creating a new segment commitlog_rotation_threshold_in_mb: 128 # commitlog_sync may be either "periodic" or "batch." # When in batch mode, Cassandra won't ack writes until the commit log # has been fsynced to disk. It will wait up to # CommitLogSyncBatchWindowInMS milliseconds for other writes, before # performing the sync. commitlog_sync: periodic # the other option is "periodic" where writes may be acked immediately # and the CommitLog is simply synced every commitlog_sync_period_in_ms # milliseconds. commitlog_sync_period_in_ms: 10000 # any class that implements the SeedProvider interface and has a constructor that takes a Map<String, String> of # parameters will do. seed_provider: # Addresses of hosts that are deemed contact points. # Cassandra nodes use this list of hosts to find each other and learn # the topology of the ring. You must change this if you are running # multiple nodes! - class_name: org.apache.cassandra.locator.SimpleSeedProvider parameters: # seeds is actually a comma-delimited list of addresses. - seeds: "10.17.91.132,10.17.91.140,10.17.91.138" # emergency pressure valve: each time heap usage after a full (CMS) # garbage collection is above this fraction of the max, Cassandra will # flush the largest memtables. # # Set to 1.0 to disable. Setting this lower than # CMSInitiatingOccupancyFraction is not likely to be useful. # # RELYING ON THIS AS YOUR PRIMARY TUNING MECHANISM WILL WORK POORLY: # it is most effective under light to moderate load, or read-heavy # workloads; under truly massive write load, it will often be too # little, too late. flush_largest_memtables_at: 0.75 # emergency pressure valve #2: the first time heap usage after a full # (CMS) garbage collection is above this fraction of the max, # Cassandra will reduce cache maximum _capacity_ to the given fraction # of the current _size_. Should usually be set substantially above # flush_largest_memtables_at, since that will have less long-term # impact on the system. # # Set to 1.0 to disable. Setting this lower than # CMSInitiatingOccupancyFraction is not likely to be useful. reduce_cache_sizes_at: 0.85 reduce_cache_capacity_to: 0.6 # For workloads with more data than can fit in memory, Cassandra's # bottleneck will be reads that need to fetch data from # disk. "concurrent_reads" should be set to (16 * number_of_drives) in # order to allow the operations to enqueue low enough in the stack # that the OS and drives can reorder them. # # On the other hand, since writes are almost never IO bound, the ideal # number of "concurrent_writes" is dependent on the number of cores in # your system; (8 * number_of_cores) is a good rule of thumb. concurrent_reads: 512 concurrent_writes: 128 # Total memory to use for memtables. Cassandra will flush the largest # memtable when this much memory is used. Prefer using this to # the older, per-ColumnFamily memtable flush thresholds. # If omitted, Cassandra will set it to 1/3 of the heap. # If set to 0, only the old flush thresholds are used. # memtable_total_space_in_mb: 2048 # This sets the amount of memtable flush writer threads. These will # be blocked by disk io, and each one will hold a memtable in memory # while blocked. If you have a large heap and many data directories, # you can increase this value for better flush performance. # By default this will be set to the amount of data directories defined. #memtable_flush_writers: 1 # the number of full memtables to allow pending flush, that is, # waiting for a writer thread. At a minimum, this should be set to # the maximum number of secondary indexes created on a single CF. memtable_flush_queue_size: 4 # Buffer size to use when performing contiguous column slices. # Increase this to the size of the column slices you typically perform sliced_buffer_size_in_kb: 64 # TCP port, for commands and data storage_port: 7000 # Address to bind to and tell other Cassandra nodes to connect to. You # _must_ change this if you want multiple nodes to be able to # communicate! # # Leaving it blank leaves it up to InetAddress.getLocalHost(). This # will always do the Right Thing *if* the node is properly configured # (hostname, name resolution, etc), and the Right Thing is to use the # address associated with the hostname (it might not be). # # Setting this to 0.0.0.0 is always wrong. listen_address: 10.17.91.132 # The address to bind the Thrift RPC service to -- clients connect # here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if # you want Thrift to listen on all interfaces. # # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). rpc_address: 0.0.0.0 # port for Thrift to listen for clients on rpc_port: 9160 # enable or disable keepalive on rpc connections rpc_keepalive: true # Cassandra uses thread-per-client for client RPC. This can # be expensive in memory used for thread stack for a large # enough number of clients. (Hence, connection pooling is # very, very strongly recommended.) # # Uncomment rpc_min|max|thread to set request pool size. # You would primarily set max as a safeguard against misbehaved # clients; if you do hit the max, Cassandra will block until # one disconnects before accepting more. The defaults are # min of 16 and max unlimited. # # rpc_min_threads: 16 # rpc_max_threads: 2048 # uncomment to set socket buffer sizes on rpc connections # rpc_send_buff_size_in_bytes: # rpc_recv_buff_size_in_bytes: # Frame size for thrift (maximum field length). # 0 disables TFramedTransport in favor of TSocket. This option # is deprecated; we strongly recommend using Framed mode. thrift_framed_transport_size_in_mb: 15 # The max length of a thrift message, including all fields and # internal thrift overhead. thrift_max_message_length_in_mb: 16 # Set to true to have Cassandra create a hard link to each sstable # flushed or streamed locally in a backups/ subdirectory of the # Keyspace data. Removing these links is the operator's # responsibility. incremental_backups: false # Whether or not to take a snapshot before each compaction. Be # careful using this option, since Cassandra won't clean up the # snapshots for you. Mostly useful if you're paranoid when there # is a data format change. snapshot_before_compaction: false # change this to increase the compaction thread's priority. In java, 1 is the # lowest priority and that is our default. # compaction_thread_priority: 1 # Add column indexes to a row after its contents reach this size. # Increase if your column values are large, or if you have a very large # number of columns. The competing causes are, Cassandra has to # deserialize this much of the row to read a single column, so you want # it to be small - at least if you do many partial-row reads - but all # the index data is read for each access, so you don't want to generate # that wastefully either. column_index_size_in_kb: 64 # Size limit for rows being compacted in memory. Larger rows will spill # over to disk and use a slower two-pass compaction process. A message # will be logged specifying the row key. in_memory_compaction_limit_in_mb: 64 # Number of compaction threads. This default to the number of processors, # enabling multiple compactions to execute at once. Using more than one # thread is highly recommended to preserve read performance in a mixed # read/write workload as this avoids sstables from accumulating during long # running compactions. The default is usually fine and if you experience # problems with compaction running too slowly or too fast, you should look at # compaction_throughput_mb_per_sec first. # Uncomment to make compaction mono-threaded. #concurrent_compactors: 1 # Throttles compaction to the given total throughput across the entire # system. The faster you insert data, the faster you need to compact in # order to keep the sstable count down, but in general, setting this to # 16 to 32 times the rate you are inserting data is more than sufficient. # Setting this to 0 disables throttling. compaction_throughput_mb_per_sec: 0 # Track cached row keys during compaction, and re-cache their new # positions in the compacted sstable. Disable if you use really large # key caches. compaction_preheat_key_cache: true # Time to wait for a reply from other nodes before failing the command rpc_timeout_in_ms: 10000 # phi value that must be reached for a host to be marked down. # most users should never need to adjust this. # phi_convict_threshold: 8 # endpoint_snitch -- Set this to a class that implements # IEndpointSnitch, which will let Cassandra know enough # about your network topology to route requests efficiently. # Out of the box, Cassandra provides # - org.apache.cassandra.locator.SimpleSnitch: # Treats Strategy order as proximity. This improves cache locality # when disabling read repair, which can further improve throughput. # - org.apache.cassandra.locator.RackInferringSnitch: # Proximity is determined by rack and data center, which are # assumed to correspond to the 3rd and 2nd octet of each node's # IP address, respectively # org.apache.cassandra.locator.PropertyFileSnitch: # - Proximity is determined by rack and data center, which are # explicitly configured in cassandra-topology.properties. endpoint_snitch: org.apache.cassandra.locator.BriskSimpleSnitch # dynamic_snitch -- This boolean controls whether the above snitch is # wrapped with a dynamic snitch, which will monitor read latencies # and avoid reading from hosts that have slowed (due to compaction, # for instance) dynamic_snitch: true # controls how often to perform the more expensive part of host score # calculation dynamic_snitch_update_interval_in_ms: 100 # controls how often to reset all host scores, allowing a bad host to # possibly recover dynamic_snitch_reset_interval_in_ms: 600000 # if set greater than zero and read_repair_chance is < 1.0, this will allow # 'pinning' of replicas to hosts in order to increase cache capacity. # The badness threshold will control how much worse the pinned host has to be # before the dynamic snitch will prefer other replicas over it. This is # expressed as a double which represents a percentage. Thus, a value of # 0.2 means Cassandra would continue to prefer the static snitch values # until the pinned host was 20% worse than the fastest. dynamic_snitch_badness_threshold: 0.0 # request_scheduler -- Set this to a class that implements # RequestScheduler, which will schedule incoming client requests # according to the specific policy. This is useful for multi-tenancy # with a single Cassandra cluster. # NOTE: This is specifically for requests from the client and does # not affect inter node communication. # org.apache.cassandra.scheduler.NoScheduler - No scheduling takes place # org.apache.cassandra.scheduler.RoundRobinScheduler - Round robin of # client requests to a node with a separate queue for each # request_scheduler_id. The scheduler is further customized by # request_scheduler_options as described below. request_scheduler: org.apache.cassandra.scheduler.NoScheduler # Scheduler Options vary based on the type of scheduler # NoScheduler - Has no options # RoundRobin # - throttle_limit -- The throttle_limit is the number of in-flight # requests per client. Requests beyond # that limit are queued up until # running requests can complete. # The value of 80 here is twice the number of # concurrent_reads + concurrent_writes. # - default_weight -- default_weight is optional and allows for # overriding the default which is 1. # - weights -- Weights are optional and will default to 1 or the # overridden default_weight. The weight translates into how # many requests are handled during each turn of the # RoundRobin, based on the scheduler id. # # request_scheduler_options: # throttle_limit: 80 # default_weight: 5 # weights: # Keyspace1: 1 # Keyspace2: 5 # request_scheduler_id -- An identifer based on which to perform # the request scheduling. Currently the only valid option is keyspace. # request_scheduler_id: keyspace # The Index Interval determines how large the sampling of row keys # is for a given SSTable. The larger the sampling, the more effective # the index is at the cost of space. index_interval: 128 # Enable or disable inter-node encryption # Default settings are TLS v1, RSA 1024-bit keys (it is imperative that # users generate their own keys) TLS_RSA_WITH_AES_128_CBC_SHA as the cipher # suite for authentication, key exchange and encryption of the actual data transfers. # NOTE: No custom encryption options are enabled at the moment # The available internode options are : all, none # # The passwords used in these options must match the passwords used when generating # the keystore and truststore. For instructions on generating these files, see: # <a href="http://download.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore" rel="nofollow">http://download.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore</a> encryption_options: internode_encryption: none keystore: conf/.keystore keystore_password: cassandra truststore: conf/.truststore truststore_password: cassandra Here is what we have in the syslog for that hadoop job: 2011-05-25 09:12:18,364 INFO org.apache.hadoop.mapred.TaskRunner: Creating symlink: /tmp/hadoop-cassandra/mapred/local/taskTracker/distcache/6439118782556776681_-344378518_662629255/null/tmp/hive-root/hive_2011-05-25_09-11-25_939_4145824745557183039/-mr-10003/2afcfc94-f85a-40ca-9695-b8d977a2d619 <- /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/attempt_201105241523_0004_r_000000_2/work/HIVE_PLAN2afcfc94-f85a-40ca-9695-b8d977a2d619 2011-05-25 09:12:18,371 INFO org.apache.hadoop.filecache.TrackerDistributedCacheManager: Creating symlink: /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/jars/.job.jar.crc <- /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/attempt_201105241523_0004_r_000000_2/work/.job.jar.crc 2011-05-25 09:12:18,372 INFO org.apache.hadoop.filecache.TrackerDistributedCacheManager: Creating symlink: /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/jars/job.jar <- /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/attempt_201105241523_0004_r_000000_2/work/job.jar 2011-05-25 09:12:18,374 INFO org.apache.hadoop.filecache.TrackerDistributedCacheManager: Creating symlink: /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/jars/org <- /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/attempt_201105241523_0004_r_000000_2/work/org 2011-05-25 09:12:18,376 INFO org.apache.hadoop.filecache.TrackerDistributedCacheManager: Creating symlink: /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/jars/META-INF <- /tmp/hadoop-cassandra/mapred/local/taskTracker/root/jobcache/job_201105241523_0004/attempt_201105241523_0004_r_000000_2/work/META-INF 2011-05-25 09:12:18,384 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 2011-05-25 09:12:18,477 WARN org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Metrics system not started: Cannot locate configuration: tried hadoop-metrics2-reducetask.properties, hadoop-metrics2.properties 2011-05-25 09:12:18,596 INFO org.apache.cassandra.config.DatabaseDescriptor: Loading settings from file:/etc/brisk/cassandra/cassandra.yaml 2011-05-25 09:12:18,711 INFO org.apache.cassandra.config.DatabaseDescriptor: DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap 2011-05-25 09:12:18,874 INFO org.apache.hadoop.mapred.ReduceTask: ShuffleRamManager: MemoryLimit=167031600, MaxSingleShuffleLimit=41757900 2011-05-25 09:12:18,881 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Thread started: Thread for merging on-disk files 2011-05-25 09:12:18,881 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Thread started: Thread for merging in memory files 2011-05-25 09:12:18,881 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Thread waiting: Thread for merging on-disk files 2011-05-25 09:12:18,883 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Need another 3 map output(s) where 0 is already in progress 2011-05-25 09:12:18,883 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Thread started: Thread for polling Map Completion Events 2011-05-25 09:12:18,883 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Scheduled 0 outputs (0 slow hosts and0 dup hosts) 2011-05-25 09:12:23,884 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Scheduled 3 outputs (0 slow hosts and0 dup hosts) 2011-05-25 09:12:24,224 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 copy failed: attempt_201105241523_0004_m_000000_0 from cass02 2011-05-25 09:12:24,224 WARN org.apache.hadoop.mapred.ReduceTask: java.net.UnknownHostException: cass02 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at sun.net.NetworkClient.doConnect(NetworkClient.java:158) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getInputStream(ReduceTask.java:1602) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.setupSecureConnection(ReduceTask.java:1559) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getMapOutput(ReduceTask.java:1467) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.copyOutput(ReduceTask.java:1378) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.run(ReduceTask.java:1310) 2011-05-25 09:12:24,225 INFO org.apache.hadoop.mapred.ReduceTask: Task attempt_201105241523_0004_r_000000_2: Failed fetch #1 from attempt_201105241523_0004_m_000000_0 2011-05-25 09:12:24,225 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 adding host cass02 to penalty box, next contact in 4 seconds 2011-05-25 09:12:24,225 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2: Got 1 map-outputs from previous failures 2011-05-25 09:12:24,260 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 copy failed: attempt_201105241523_0004_m_000001_0 from cass03 2011-05-25 09:12:24,260 WARN org.apache.hadoop.mapred.ReduceTask: java.net.UnknownHostException: cass03 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at sun.net.NetworkClient.doConnect(NetworkClient.java:158) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getInputStream(ReduceTask.java:1602) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.setupSecureConnection(ReduceTask.java:1559) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getMapOutput(ReduceTask.java:1467) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.copyOutput(ReduceTask.java:1378) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.run(ReduceTask.java:1310) 2011-05-25 09:12:24,260 INFO org.apache.hadoop.mapred.ReduceTask: Task attempt_201105241523_0004_r_000000_2: Failed fetch #1 from attempt_201105241523_0004_m_000001_0 2011-05-25 09:12:24,260 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 adding host cass03 to penalty box, next contact in 4 seconds 2011-05-25 09:12:24,260 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2: Got 1 map-outputs from previous failures 2011-05-25 09:12:29,360 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 Scheduled 2 outputs (0 slow hosts and0 dup hosts) 2011-05-25 09:12:29,362 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 copy failed: attempt_201105241523_0004_m_000000_0 from cass02 2011-05-25 09:12:29,362 WARN org.apache.hadoop.mapred.ReduceTask: java.net.UnknownHostException: cass02 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at sun.net.NetworkClient.doConnect(NetworkClient.java:158) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getInputStream(ReduceTask.java:1602) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.setupSecureConnection(ReduceTask.java:1559) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getMapOutput(ReduceTask.java:1467) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.copyOutput(ReduceTask.java:1378) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.run(ReduceTask.java:1310) 2011-05-25 09:12:29,362 INFO org.apache.hadoop.mapred.ReduceTask: Task attempt_201105241523_0004_r_000000_2: Failed fetch #2 from attempt_201105241523_0004_m_000000_0 2011-05-25 09:12:29,362 INFO org.apache.hadoop.mapred.ReduceTask: Failed to fetch map-output from attempt_201105241523_0004_m_000000_0 even after MAX_FETCH_RETRIES_PER_MAP retries... or it is a read error, reporting to the JobTracker 2011-05-25 09:12:29,362 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 copy failed: attempt_201105241523_0004_m_000001_0 from cass03 2011-05-25 09:12:29,362 WARN org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2 adding host cass02 to penalty box, next contact in 8 seconds 2011-05-25 09:12:29,363 INFO org.apache.hadoop.mapred.ReduceTask: attempt_201105241523_0004_r_000000_2: Got 1 map-outputs from previous failures 2011-05-25 09:12:29,363 WARN org.apache.hadoop.mapred.ReduceTask: java.net.UnknownHostException: cass03 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at sun.net.NetworkClient.doConnect(NetworkClient.java:158) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getInputStream(ReduceTask.java:1602) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.setupSecureConnection(ReduceTask.java:1559) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getMapOutput(ReduceTask.java:1467) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.copyOutput(ReduceTask.java:1378) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.run(ReduceTask.java:1310) 2011-05-25 09:12:29,363 INFO org.apache.hadoop.mapred.ReduceTask: Task attempt_201105241523_0004_r_000000_2: Failed fetch #2 from attempt_201105241523_0004_m_000001_0 2011-05-25 09:12:29,363 INFO org.apache.hadoop.mapred.ReduceTask: Failed to fetch map-output from attempt_201105241523_0004_m_000001_0 even after MAX_FETCH_RETRIES_PER_MAP retries... or it is a read error, reporting to the JobTracker 2011-05-25 09:12:29,363 FATAL org.apache.hadoop.mapred.ReduceTask: Shuffle failed with too many fetch failures and insufficient progress!Killing task attempt_201105241523_0004_r_000000_2. Yewei on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-102 Tue, 24 May 2011 22:24:54 +0000 Yewei 102@http://www.datastax.com/support-forums/ In the hive-site.xml file under brisk, you could add the following properties to point to the metastore on 192.168.*.***: <property> <name>cassandra.connection.host</name> <value>192.168.*.***</value> </property> Yewei on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-101 Tue, 24 May 2011 22:01:34 +0000 Yewei 101@http://www.datastax.com/support-forums/ From the error, it looks like hive is not able to connect to the metastore. By default, it will connect to the localhost. Would you please let me know the procedure of starting your cluster and your hive? Where did you run ./brisk hive? When you run ./nodetool -h XXX ring, what is the result? On the server where you run ./brisk hive, what is the value of listen_address in the resources/cassandra/conf/cassandra.yaml? Thank you. Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-100 Tue, 24 May 2011 21:02:28 +0000 Prosperent 100@http://www.datastax.com/support-forums/ No, actually, that appears to have been my oversight. I typically just bind that to my internal ip for that node. I removed that and it took care of the issue. Thank you for your patience. This is still a new beast for us. This got us so we are now able to load the demo site and run the map reduce task. The map task completes, but reduce gives us some errors. I am thinking it is again something to do with our host configuration. Ended Job = job_201105241523_0003 with errors FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask Checking the errors in the hadoop log I see: Shuffle Error: Exceeded MAX_FAILED_UNIQUE_FETCHES; bailing-out. Shuffle Error: Exceeded MAX_FAILED_UNIQUE_FETCHES; bailing-out. Shuffle Error: Exceeded MAX_FAILED_UNIQUE_FETCHES; bailing-out. Shuffle Error: Exceeded MAX_FAILED_UNIQUE_FETCHES; bailing-out. tjake on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-98 Tue, 24 May 2011 19:57:11 +0000 tjake 98@http://www.datastax.com/support-forums/ I'll need to reproduce this and see what the problem is... any reason you don't want to bind the rpc to 0.0.0.0? This is what we recommend in the docs. Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-97 Tue, 24 May 2011 19:41:51 +0000 Prosperent 97@http://www.datastax.com/support-forums/ Thanks, configured that parameter, but still get a localhost error: create external table Portfolios(row_key string, column_name string, value string) > STORED BY 'org.apache.hadoop.hive.cassandra.CassandraStorageHandler' > WITH SERDEPROPERTIES ("cassandra.columns.mapping" = ":key,:column,:value", > "cassandra.ks.name" = "PortfolioDemo", > "cassandra.ks.repfactor" = "2", > "cassandra.ks.strategy" = "org.apache.cassandra.locator.SimpleStrategy", > "cassandra.cf.name" = "Portfolios" , > "cassandra.host" = "10.17.91.132" , > "cassandra.port" = "9160", > "cassandra.partitioner" = "org.apache.cassandra.dht.RandomPartitioner") > TBLPROPERTIES ( > "cassandra.input.split.size" = "64000", > "cassandra.range.size" = "1000", > "cassandra.slice.predicate.size" = "1000"); FAILED: Error in metadata: org.apache.cassandra.hadoop.hive.metastore.CassandraHiveMetaStoreException: There was a problem with the Cassandra Hive MetaStore: Could not connect to Cassandra. Reason: Error connecting to node localhost I was able to get the data fro mthe tutorial into the system, but starting the java server at this step: 4)Start the web service. cd website java -jar start.jar It appears that the web server is also trying to connect to localhost for cassandra. Where can this be configured? tjake on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-96 Tue, 24 May 2011 17:15:51 +0000 tjake 96@http://www.datastax.com/support-forums/ You can specify the property "cassandra.host" <a href="http://www.datastax.com/docs/0.8/brisk/about_hive#reference-serdeproperties-and-tblproperties" rel="nofollow">http://www.datastax.com/docs/0.8/brisk/about_hive#reference-serdeproperties-and-tblproperties</a> Prosperent on "There was a problem with the Cassandra Hive MetaStore" http://www.datastax.com/support-forums/topic/there-was-a-problem-with-the-cassandra-hive-metastore#post-95 Tue, 24 May 2011 16:57:16 +0000 Prosperent 95@http://www.datastax.com/support-forums/ I'm sure this is a simple fix, but i'm just not seeing where to make the change. We setup a 3 node cluster with Brisk. Everything is running fine (according to opscenter). I started up the HIVE tutorial to check out hadoop. Running Ubuntu 10.04 I issue: brisk hive No problem, I then try to create the table: CREATE TABLE invites (foo INT, bar STRING) PARTITIONED BY (ds STRING) TBLPROPERTIES ("cassandra.ks.name" = "Hive", "cassandra.ks.repfactor" = "2", "cassandra.ks.strategy" = "org.apache.cassandra.locator.NetworkTopologyStrategy", "cassandra.input.split.size" = "64000", "cassandra.range.size" = "100", "cassandra.slice.predicate.size" = "100" ); which results in: FAILED: Error in metadata: org.apache.cassandra.hadoop.hive.metastore.CassandraHiveMetaStoreException: There was a problem with the Cassandra Hive MetaStore: Could not connect to Cassandra. Reason: Error connecting to node localhost The issue appears to be that it is trying to connect to node: localhost when it should be using one of my internal ip addresses. I was under the impression that the ip's were grabbed fro mthe cassandra.yaml config. Is there another place that we need to change this localhost ip as well?