Brisk TaskTracker 未在多节点 Brisk 设置中启动
我有一个 3 节点 Brisk 集群 (Briskv1.0_beta2)。 Cassandra 工作正常（所有三个节点都能看到对方，并且数据在环上保持平衡）。我使用 brisk cassandra -t 命令启动节点。但是，我无法运行任何 Hive 或 Pig 作业。当我这样做时，我收到一个异常，说它无法连接到任务跟踪器。
在启动过程中，我在日志中看到以下内容：
TaskTracker.java (line 695) TaskTracker up at: localhost.localdomain/127.0.0.1:34928
然而，几行之后，我看到了以下内容：
Retrying connect to server: localhost.localdomain/127.0.0.1:8012. Already tried 9 time(s).
INFO [TASK-TRACKER-INIT] RPC.java (line 321) Server at localhost.localdomain/127.0.0.1:8012 not available yet, Zzzzz...
只要我的集群正在运行，这些行就会不停地重复。
我的 cassandra.yaml 文件指定盒子 IP（不是 0.0.0.0 或 localhost）作为listen_address，并且 rpc_address 设置为 0.0.0.0
为什么客户端尝试连接到日志显示任务跟踪器使用的不同端口？是否可以在任何地方指定这些地址/端口？
I have a 3 node Brisk cluster (Briskv1.0_beta2). Cassandra is working fine (all three nodes see each other and data is balanced across the ring). I started the nodes with the brisk cassandra -t command. I cannot, however, run any Hive or Pig jobs. When I do, I get an exception saying that it cannot connect to the task tracker.
During the startup process, I see the following in the log:
TaskTracker.java (line 695) TaskTracker up at: localhost.localdomain/127.0.0.1:34928
A few lines later, however, I see this:
Retrying connect to server: localhost.localdomain/127.0.0.1:8012. Already tried 9 time(s).
INFO [TASK-TRACKER-INIT] RPC.java (line 321) Server at localhost.localdomain/127.0.0.1:8012 not available yet, Zzzzz...
Those lines are repeated non-stop as long as my cluster is running.
My cassandra.yaml file specifies the box IP (not 0.0.0.0 or localhost) as the listen_address and the rpc_address is set to 0.0.0.0
Why is the client attempting to connect to a different port than the log shows the task tracker as using? Is there anywhere these addresses/ports can be specified?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我明白了这一点。如果其他人也遇到同样的问题，情况如下：
Brisk 使用 Cassandra 集群种子列表中的第一个条目来选择初始 jobtracker。我的一个节点的种子列表中有 127.0.0.1。这适用于 Cassandra 设置，因为集群中的所有其他节点都连接到该盒子以获取集群拓扑，但这不适用于作业跟踪器选择。
I figured this out. In case anyone else has the same issues, here's what was going on:
Brisk uses the first entry in the Cassandra cluster's seed list to pick the initial jobtracker. One of my nodes had 127.0.0.1 in the seed list. This worked for the Cassandra setup since all the other nodes in the cluster connected to that box to get the cluster topology but this didn't work for the job tracker selection.
您的 jobtracker 似乎没有运行。当您运行“brisktool jobtracker”时您会看到什么？
looks like your jobtracker isn't running. What do you see when you run "brisktool jobtracker"?