You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Steven Pine (JIRA)" <ji...@apache.org> on 2012/05/21 17:30:41 UTC
[jira] [Created] (ACCUMULO-601) Cannot create or delete tables via
Java after upgrade to accumulo 1.4
Steven Pine created ACCUMULO-601:
------------------------------------
Summary: Cannot create or delete tables via Java after upgrade to accumulo 1.4
Key: ACCUMULO-601
URL: https://issues.apache.org/jira/browse/ACCUMULO-601
Project: Accumulo
Issue Type: Bug
Components: client
Affects Versions: 1.4.0
Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
Reporter: Steven Pine
Assignee: Billie Rinaldi
After upgrade I am unable to create or delete a table via java using either the
conn.tableOperations().delete(tableName);
and/or
conn.tableOperations().create(tableName);
The error presents itself by hanging the code when it executes this line in the code.
Important:
Table scans via java are working fine.
Table mutations via java also work fine.
The same user account can create and deleted the table via accumulo shell.
The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280541#comment-13280541 ]
Keith Turner commented on ACCUMULO-601:
---------------------------------------
Another useful thing to do is jstack the client process that called create table. The look for the thread stack that called tabletOperations().create("") and see what that thread is doing. You could post that here.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACCUMULO-601) client fails to resolve master
hostname when not using fully qualified domain name
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner resolved ACCUMULO-601.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.1
1.5.0
Assignee: Keith Turner (was: Billie Rinaldi)
> client fails to resolve master hostname when not using fully qualified domain name
> ----------------------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Keith Turner
> Fix For: 1.5.0, 1.4.1
>
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281608#comment-13281608 ]
Keith Turner commented on ACCUMULO-601:
---------------------------------------
The zookeeper path looks right. Did you try changing the contents of the file <ACCUMULO_HOME>/conf/masters to contain the FQDN and restarting that master?
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACCUMULO-601) client fails to resolve master
hostname when not using fully qualified domain name
Posted by "Adam Fuchs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Fuchs updated ACCUMULO-601:
--------------------------------
Summary: client fails to resolve master hostname when not using fully qualified domain name (was: Cannot create or delete tables via Java after upgrade to accumulo 1.4)
> client fails to resolve master hostname when not using fully qualified domain name
> ----------------------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281261#comment-13281261 ]
Keith Turner commented on ACCUMULO-601:
---------------------------------------
I am not sure about this, but it may be that whatever is in your accumulo/conf/masters file ends up in zookeeper. Try setting that to the FQDN.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (ACCUMULO-601) Cannot create or delete
tables via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280541#comment-13280541 ]
Keith Turner edited comment on ACCUMULO-601 at 5/21/12 10:09 PM:
-----------------------------------------------------------------
Another useful thing to do is jstack the client process that called create table. Then look for the thread stack that called tabletOperations().create("") and see what that thread is doing. You could post that here.
was (Author: kturner):
Another useful thing to do is jstack the client process that called create table. The look for the thread stack that called tabletOperations().create("") and see what that thread is doing. You could post that here.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Adam Fuchs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283344#comment-13283344 ]
Adam Fuchs commented on ACCUMULO-601:
-------------------------------------
We've also had some success getting around this issue in the past by setting the domain name on all the nodes (using domainname).
The RSA message is because your ssh known hosts database doesn't have a mapping for the FQDN. The start-all.sh script uses ssh to launch processes.
Unfortunately, there are many ways to set up DNS and Linux networking, and most of them usually work for most applications. Accumulo should probably be more robust and work with a broader set of common linux networking configurations.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Steven Pine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281246#comment-13281246 ]
Steven Pine commented on ACCUMULO-601:
--------------------------------------
I think I found the problem. After turning on trace level logging I found that the code (while hanging on the create command) was repeatedly
Indicating that "Found master at <host name only>:9999 and throwing a "java.net.UnknownHostException: <host name only>
I don't believe my java code on the workstation is able to resolve <host name only> to the fully qualified host name. Causing the hanging I am seeing.
My next questions are how do I get around this:
1. Is the entry I found in Zookeeper wrong as <host name only>:9999. Should it be <Fully Qualified Hostname>:9999 ?
2. Is there something else I need to do?
3. What is the best approach to work around this issue (and what are the implications if any)?
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Steven Pine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280511#comment-13280511 ]
Steven Pine commented on ACCUMULO-601:
--------------------------------------
After narrowing down the list of jar files I needed I ran the new project and it also hangs at the same place (when it calls the create).
Below is the List of Referenced Libraries I attached to the new Project:
accumulo-core-1.4.0.jar
log4j-1.2.16.jar
zookeeper-3.3.1.jar
libthrift-0.6.1.jar
hadoop-0.20.2-core.jar
commons-logging-1.0.4.jar
slf4j-api-1.4.3.jar
slf4j-log4j-1.4.3.jar
cloudtrace-1.4.0.jar
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Steven Pine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281627#comment-13281627 ]
Steven Pine commented on ACCUMULO-601:
--------------------------------------
I tested changing conf/masters first using the IP address. That fixed it but as A side note zookeeper had the <fully qualified hostname>:9999 stored.
I also tested placing the <fully qualified hostname> into conf/masters. That also worked. During the first startup I got and RSA message "The authenticity pf host ..... can't be established" message and accepted it the first time. Subsequent starts no longer prompted and everything appears to be working normally. The value stored in zookeeper was also <fully qualified hostname>:9999.
Not sure why (when I put the IP Address in conf/masters) the IP address was converted to the <fully qualified hostname> in zookeeper instead of keeping the IP Address.
The question is whether it would be better to let it store the IP Address (making it more consistent with other zookeeper entries) and this might work better in cases where these type of tasks want to be handled via remote administration.
For now we have a workaround which is to either place the IP Address or since it doesn't matter put the fully qualified hostname into conf/masters.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281562#comment-13281562 ]
Keith Turner commented on ACCUMULO-601:
---------------------------------------
This issue was too hard to debug. What can we do to make it better? Below are some thoughts.
* Not retry on UnknownHostException. It extends IOException, so we probably catch that and retry.
* For tablet servers we put an ip address in zookeeper and metadata table I think, look into why something different is done for the master.
* Maybe make retry code log one warning after a certain amount of retries? I think some of the retry code does this.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280537#comment-13280537 ]
Keith Turner commented on ACCUMULO-601:
---------------------------------------
In 1.4 createtable and deletetable start FATE operations. You can see if any of those are stuck with the following command.
{noformat}
./bin/accumulo org.apache.accumulo.server.fate.Admin print
{noformat}
If the client can not even reach the master to start a FATE op, then the nothing will be printed.
You can also enable log4j tracing in your client code to see if this reveals anything of interest.
{code}
public class CreateTableTest {
/**
* @param args
*/
public static void main(String[] args) throws Exception {
org.apache.log4j.Logger.getLogger("org.apache.accumulo.core.client").setLevel(Level.TRACE);
ZooKeeperInstance zki = new ZooKeeperInstance("test14", "localhost");
Connector conn = zki.getConnector("user", "pass");
conn.tableOperations().create("foo1");
}
}
{code}
I saw the output below when running the program above. You can see it getting connections to the master to walk the fate operation through its steps.
{noformat}
$ ./bin/accumulo org.apache.accumulo.core.CreateTableTest
21 17:58:33,883 [impl.ThriftTransportPool] TRACE: Creating new connection to connection to 127.0.0.1:9997:9997
21 17:58:34,498 [impl.ThriftTransportPool] TRACE: Returned connection 127.0.0.1:9997:9997 (120000) ioCount : 122
21 17:58:34,584 [client.ZooKeeperInstance] TRACE: tid=12 oid=0 Looking up master location in zoocache.
21 17:58:34,596 [client.ZooKeeperInstance] TRACE: tid=12 oid=0 Found master at localhost:9999 in 0.005 secs
21 17:58:34,601 [impl.ThriftTransportPool] TRACE: Creating new connection to connection to localhost:9999:9999
21 17:58:34,660 [impl.ThriftTransportPool] TRACE: Returned connection localhost:9999:9999 (0) ioCount : 116
21 17:58:34,661 [client.ZooKeeperInstance] TRACE: tid=12 oid=1 Looking up master location in zoocache.
21 17:58:34,661 [client.ZooKeeperInstance] TRACE: tid=12 oid=1 Found master at localhost:9999 in 0.000 secs
21 17:58:34,662 [impl.ThriftTransportPool] TRACE: Using existing connection to localhost:9999:9999
21 17:58:34,709 [impl.ThriftTransportPool] TRACE: Returned connection localhost:9999:9999 (0) ioCount : 168
21 17:58:34,709 [client.ZooKeeperInstance] TRACE: tid=12 oid=2 Looking up master location in zoocache.
21 17:58:34,711 [client.ZooKeeperInstance] TRACE: tid=12 oid=2 Found master at localhost:9999 in 0.000 secs
21 17:58:34,712 [impl.ThriftTransportPool] TRACE: Using existing connection to localhost:9999:9999
21 17:58:35,748 [impl.ThriftTransportPool] TRACE: Returned connection localhost:9999:9999 (0) ioCount : 132
21 17:58:35,749 [client.ZooKeeperInstance] TRACE: tid=12 oid=3 Looking up master location in zoocache.
21 17:58:35,749 [client.ZooKeeperInstance] TRACE: tid=12 oid=3 Found master at localhost:9999 in 0.000 secs
21 17:58:35,749 [impl.ThriftTransportPool] TRACE: Using existing connection to localhost:9999:9999
21 17:58:35,806 [impl.ThriftTransportPool] TRACE: Returned connection localhost:9999:9999 (0) ioCount : 96
$
{noformat}
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "John Vines (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280230#comment-13280230 ]
John Vines commented on ACCUMULO-601:
-------------------------------------
If the shell works fine and your code does not, that leads me to think that your code is depending on the old API. How are you executing your jar? And are there any cloudbase-1.3.4 jars shaded with your code? Some of the code for create/delete changed, which would explain that code breaking between 1.3.x and 1.4.
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Steven Pine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280517#comment-13280517 ]
Steven Pine commented on ACCUMULO-601:
--------------------------------------
I wanted to pass on my further testing for completness.
I still have not been able to resolve this problem. It still hangs during the create or delete from my workstation it doesn't matter whether I run this inside eclipse or from the command line.
I Tested the following:
Server Side (Linux):
1. Ran my java source code on the Server and it works.
2. I Generated a jar via Eclipse (after dumb-ing it down to 1.6 jre) and it also ran fine on the Server.
Workstation side (Windows):
1. Running the java source via Eclipse hangs at the create line of the code.
2. Running the jar from the Windows command line also hangs at the create line.
Note: I re-copied the jar files from the server to the Workstation just to ensure that I was running with the exact same jar files.
This narrows down my ideas to two possibilities:
1. Some Firewall rule is intercepting traffic so that it hangs and never completes (however I can Scan and perform mutation on tables from my workstation).
2. There is some kind of dependency be it Linux or some object on the Server that the create/delete class depends on that is not there in Windows.
Note: Keeping in mind that I can run java code to scan and perform mutations against Accumulo tables and they work fine from within Eclipse (on my Workstation)leads me to lean more towards option 2 (unless there is some specific traffic that occurs when creating/deleting tables that does not occur when you scan or perform mutations).
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-601) Cannot create or delete tables
via Java after upgrade to accumulo 1.4
Posted by "Steven Pine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281605#comment-13281605 ]
Steven Pine commented on ACCUMULO-601:
--------------------------------------
Check inside zookeeper and I believe I found the node where it is pulling this value from. Can you confirm this?
get /accumulo/<Instance ID>/masters/lock/lock-<8 digit number>
Note: Values in <> will be specific to the Accumulo cloud you have installed.
The get yields the value we are seeing in the trace: <host name only>:9999
> Cannot create or delete tables via Java after upgrade to accumulo 1.4
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-601
> URL: https://issues.apache.org/jira/browse/ACCUMULO-601
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Environment: Cloud was upgraded from Cloudbase 1.3.4 to Accumulo 1.3.5 and then upgraded to accumulo 1.4.0. Hadoop version is 0.20.2r911707
> Reporter: Steven Pine
> Assignee: Billie Rinaldi
>
> After upgrade I am unable to create or delete a table via java using either the
> conn.tableOperations().delete(tableName);
> and/or
> conn.tableOperations().create(tableName);
> The error presents itself by hanging the code when it executes this line in the code.
> Important:
> Table scans via java are working fine.
> Table mutations via java also work fine.
> The same user account can create and deleted the table via accumulo shell.
> The cause of the code hanging cannot be determined further since there is nothing in the Eclipse logs or Server logs that provide any more information.
> I can verify that the connection to Zookeeper completes successfully... however there is no indication after that on the Server side that a call is being made to Accumulo to create/delete the table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira