Support Forums : DataStax

DataStax Support Forums » DataStax Enterprise

Analytics nodes system.log error on DSE 1.0.2

(6 posts) (4 voices)

Started 1 year ago by
Latest reply from mbulman
This topic is not resolved

Tags:

Anonymous
Unregistered

I have DSE 1.0.2 installed on 4 nodes (Two Cassandra and Two Analytics):

./nodetool -h localhost ring
Address DC Rack Status State Load Owns Token
127605887595351923798765477786913079296
10.40.199.205 Cassandra rack1 Up Normal 698.82 MB 25.00% 0
10.40.199.206 Analytics rack1 Up Normal 694.54 MB 25.00% 42535295865117307932921825928971026432
10.40.199.207 Cassandra rack1 Up Normal 683.75 MB 25.00% 85070591730234615865843651857942052864
10.40.199.208 Analytics rack1 Up Normal 674.49 MB 25.00% 127605887595351923798765477786913079296

dsetool jobtracker
10.40.199.206:8012

The system.log on two Analytics nodes has following errors:

INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:33,924 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 1 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:34,934 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 2 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:35,944 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 3 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:36,954 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 4 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:37,964 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 5 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:38,974 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 6 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:39,984 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 7 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:40,994 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 8 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:42,004 Client.java (line 629) Retrying connect to server: nyctweb01d.homebox.com/10.40.199.205:8012. Already tried 9 time(s).
INFO [TASK-TRACKER-INIT] 2012-04-17 11:11:42,005 RPC.java (line 321) Server at nyctweb01d.homebox.com/10.40.199.205:8012 not available yet, Zzzzz...

Did I missed something? Please help.

Posted 1 year ago #
thepaul
Moderator

Have you checked whether those analytics nodes actually can connect to port 8012 on 10.40.199.205?

You may be able to verify with telnet.

$ telnet 10.40.199.205 8012 $ telnet nyctweb01d.homebox.com 8012

Posted 1 year ago #
Anonymous
Unregistered

As I know, port 8012 is Hadoop Job Tracker client port.

10.40.199.205 is Cassandra node not Analytics not. From the ring you can see. Should it has 8012 port on Cassandra node? Telnet confused on 10.40.199.205 8012.

The jobtracker is on 10.40.199.206:8012.

Posted 1 year ago #
joaquin
Administrator

Hello lh,

Was this problem resolved? Sometimes the TT's get confused as to which machine to contact depending on the order they were booted and which version of DSE you're running.

Could you try dsetool movejt 10.40.199.206? This should notify all TT's.

Thanks,
Joaquin

Posted 1 year ago #
Anonymous
Unregistered

After upgrade to DSE 2.0-1 (Changed system.log file location in log4j.appender.R.File), the new system.log file only has followings:

$ cat system.log
INFO [main] 2012-04-18 15:41:59,138 AbstractCassandraDaemon.java (line 105) Logging initialized
INFO [main] 2012-04-18 15:42:00,249 AbstractCassandraDaemon.java (line 105) Logging initialized

Looks like it doesn't write to the system.log file anymore. When I started the node, it shows the system log on screen. Did I missed any settings? Where to find the more system log detail?

Thanks,

Posted 1 year ago #
mbulman
Key Master

lh,

This question was asked via our official support channel by one of your colleagues and resolved. If you continue to have issues with this or anything else, please use the official support system to ensure that you receive timely responses.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.