[jira] [Resolved] (ACCUMULO-2993) division by 0
[
https://issues.apache.org/jira/browse/ACCUMULO-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved ACCUMULO-2993.
-
Resolution: Fixed
> division by 0
> -
>
> Key: ACCUMULO-2993
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2993
> Project: Accumulo
> Issue Type: Bug
> Components: scripts
>Reporter: Eric Newton
>Assignee: Mike Drob
>Priority: Critical
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> /.../bin/start-server.sh: line 76: ((: 16 /.../conf/slaves: division by 0
> (error token is "/.../conf/slaves")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (ACCUMULO-2993) division by 0
[
https://issues.apache.org/jira/browse/ACCUMULO-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reassigned ACCUMULO-2993:
---
Assignee: Mike Drob
> division by 0
> -
>
> Key: ACCUMULO-2993
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2993
> Project: Accumulo
> Issue Type: Bug
> Components: scripts
>Reporter: Eric Newton
>Assignee: Mike Drob
>Priority: Critical
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> /.../bin/start-server.sh: line 76: ((: 16 /.../conf/slaves: division by 0
> (error token is "/.../conf/slaves")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (ACCUMULO-2992) Eliminate (use of) AccumuloConfiguration.getSiteConfiguration()
[
https://issues.apache.org/jira/browse/ACCUMULO-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061444#comment-14061444
]
Christopher Tubbs commented on ACCUMULO-2992:
-
I took a look at the patch, and it looks fine, but what seems to be missing is
an explanation as to why the old method was deprecated.
This code was deprecated because clients shouldn't be expected to be able to
have knowledge of, or permission to use, a server's configuration. For
backwards-compatibility and convenience, the use of this deprecated code was
left in the shell, with warnings suppressed, under the understanding that
eventually the shell would cease to use site configuration at all at some
point. Refactoring to use a different method doesn't address the original
issue, but just moves the concerns to a new location.
The use of site configuration should continue to be considered deprecated
within client code (including the shell), though, but that's not obvious with
this patch, which in removing the use of deprecated code, appears to have
resolved any concerns. Perhaps along with this patch, there's some comment
which can be made to clarify in the code to future developers that the use of
SiteConfiguration now (vs. the old method) should be considered deprecated in
the shell?
> Eliminate (use of) AccumuloConfiguration.getSiteConfiguration()
> ---
>
> Key: ACCUMULO-2992
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2992
> Project: Accumulo
> Issue Type: Improvement
>Reporter: Bill Havanki
>Assignee: Bill Havanki
>Priority: Trivial
> Labels: configuration
> Fix For: 1.6.1, 1.7.0
>
>
> The static method {{AccumuloConfiguration.getSiteConfiguration()}} has been
> deprecated for a long time. [~ecn] got rid of a lot of uses in ACCUMULO-2401.
> This ticket is to get rid of the rest. Each call can be replaced with:
> {code}
> SiteConfiguration.getInstance(DefaultConfiguration.getInstance());
> {code}
> The method itself can also be eliminated, as {{AccumuloConfiguration}} is not
> public API, assuming the elimination would not cause a problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (ACCUMULO-2993) division by 0
Eric Newton created ACCUMULO-2993:
-
Summary: division by 0
Key: ACCUMULO-2993
URL: https://issues.apache.org/jira/browse/ACCUMULO-2993
Project: Accumulo
Issue Type: Bug
Components: scripts
Reporter: Eric Newton
Priority: Critical
Fix For: 1.7.0
{noformat}
/.../bin/start-server.sh: line 76: ((: 16 /.../conf/slaves: division by 0
(error token is "/.../conf/slaves")
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACCUMULO-2992) Eliminate (use of) AccumuloConfiguration.getSiteConfiguration()
[
https://issues.apache.org/jira/browse/ACCUMULO-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Havanki updated ACCUMULO-2992:
---
Status: Patch Available (was: In Progress)
> Eliminate (use of) AccumuloConfiguration.getSiteConfiguration()
> ---
>
> Key: ACCUMULO-2992
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2992
> Project: Accumulo
> Issue Type: Improvement
>Reporter: Bill Havanki
>Assignee: Bill Havanki
>Priority: Trivial
> Labels: configuration
> Fix For: 1.6.1, 1.7.0
>
>
> The static method {{AccumuloConfiguration.getSiteConfiguration()}} has been
> deprecated for a long time. [~ecn] got rid of a lot of uses in ACCUMULO-2401.
> This ticket is to get rid of the rest. Each call can be replaced with:
> {code}
> SiteConfiguration.getInstance(DefaultConfiguration.getInstance());
> {code}
> The method itself can also be eliminated, as {{AccumuloConfiguration}} is not
> public API, assuming the elimination would not cause a problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (ACCUMULO-2992) Eliminate (use of) AccumuloConfiguration.getSiteConfiguration()
Bill Havanki created ACCUMULO-2992:
--
Summary: Eliminate (use of)
AccumuloConfiguration.getSiteConfiguration()
Key: ACCUMULO-2992
URL: https://issues.apache.org/jira/browse/ACCUMULO-2992
Project: Accumulo
Issue Type: Improvement
Reporter: Bill Havanki
Assignee: Bill Havanki
Priority: Trivial
Fix For: 1.6.1, 1.7.0
The static method {{AccumuloConfiguration.getSiteConfiguration()}} has been
deprecated for a long time. [~ecn] got rid of a lot of uses in ACCUMULO-2401.
This ticket is to get rid of the rest. Each call can be replaced with:
{code}
SiteConfiguration.getInstance(DefaultConfiguration.getInstance());
{code}
The method itself can also be eliminated, as {{AccumuloConfiguration}} is not
public API, assuming the elimination would not cause a problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACCUMULO-2615) Simplify server configuration caching and ZK watchers
[
https://issues.apache.org/jira/browse/ACCUMULO-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Havanki updated ACCUMULO-2615:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Simplify server configuration caching and ZK watchers
> -
>
> Key: ACCUMULO-2615
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2615
> Project: Accumulo
> Issue Type: Improvement
>Reporter: Bill Havanki
>Assignee: Bill Havanki
> Fix For: 1.6.1, 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The mechanism used for caching server-related configuration objects and
> processing ZK events could do with some simplification. For example:
> * The watcher objects obtain their corresponding configuration objects by
> reaching through the {{ServerConfiguration}} cache, instead of just having a
> more direct reference.
> * The watcher objects set log4j logging levels for both ZK and
> o.a.hadoop.io.compress to WARN, which prohibits debugging when needed. That
> should be done in log4j properties/XML instead.
> * Possible bug: {{NamespaceConfWatcher}} expires table configuration
> observers, not namespace configuration observers.
> * There is high duplication between the static and instance methods of
> {{ServerConfiguration}}. The class serves as both a cache container and a
> factory. Moreover, despite its name, it isn't actually a configuration object.
> I may be missing some subtleties of why things are as they are, so please
> fill me in as needed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (ACCUMULO-1621) document the use of the init install scripts in the user manual
[ https://issues.apache.org/jira/browse/ACCUMULO-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs resolved ACCUMULO-1621. - Resolution: Won't Fix > document the use of the init install scripts in the user manual > --- > > Key: ACCUMULO-1621 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1621 > Project: Accumulo > Issue Type: Improvement > Components: docs >Reporter: Adam Fuchs >Priority: Minor > > Accumulo comes with a nice set of scripts to set up an accumulo user and > install init scripts. It would be nice to have a concise set of installation > instructions that leverage those scripts. I put together a list of > instructions the other day for one of our installs, that is included below. > It needs review, testing, and integration into the standard docs (user manual > + README in some form). > 1. Accumulo 1.5.x should be installed using the scripts in the scripts > directory under ACCUMULO_HOME, which should be /usr/lib/accumulo. Make a > symbolic link to the /usr/lib/accumulo_1.5.0 directory (or whatever version > you're using), which is where you should put the package. > 2. Zookeeper must be installed on all machines, but it only needs to be > running on the zookeeper nodes. > 3. Make sure the HDFS /user/accumulo exists and is owned by the accumulo user > (for the trash collection issue). > 4. Make sure dfs.durable.sync (or dfs.support.append on some platforms) is > enabled. Reboot HDFS after this is set. > 5. For Accumulo with encryption, use the encryption settings from > conf/examples/crypto/accumulo-site.xml, but the other settings from > conf/examples/3GB/native-standalone* for performance. You can also bump up > the memory settings for cache and memory maps according to resources > available on the cluster. > 6. Make sure to set the instance.secret using a password generator. > 7. Make sure the accumulo-site.xml is set to only be readable by the accumulo > user. > 8. Change the accumulo-monitor user to accumulo (substitute accumulo for > accumulo_monitor in lines 28, 31, 35 of scripts/monitor-only-init.sh). This > is one way of getting past the security restrictions on the accumulo-site.xml > file and on the accumulo directory in HDFS. An alternative would be to give > the accumulo_monitor user access to those resources. > 9. From the scripts directory, run ./master-only-init.sh, ./gc-only-init.sh, > and ./monitor-only-init.sh on the master node. > 10. chown -R accumulo /usr/lib/accumulo* > 11. scp or rsync the configured accumulo directory through the cluster > 12. From the scripts directory, run ./tserver-only-init.sh on each of the > tservers. > 13. Start up all the processes using "service accumulo-master start" or the > appropriate commands on each server. > 14. Check that all the processes started using jps -m, and check that the > right number of tservers started on the monitor page. > 15. Test! Accumulo shell first, then CI if you're ambitious. > 16. Monitor the logs via the monitor page periodically over the next half > hour to see if there are any errors or warnings. Some things don't cause > errors at the API level for a while, but they show up earlier in the logs. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-1621) document the use of the init install scripts in the user manual
[ https://issues.apache.org/jira/browse/ACCUMULO-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060797#comment-14060797 ] Mike Drob commented on ACCUMULO-1621: - When we dropped RPM/DEB packaging, I believe we also dropped all of our service scripts. Can this issue be re-scoped or closed out? > document the use of the init install scripts in the user manual > --- > > Key: ACCUMULO-1621 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1621 > Project: Accumulo > Issue Type: Improvement > Components: docs >Reporter: Adam Fuchs >Priority: Minor > > Accumulo comes with a nice set of scripts to set up an accumulo user and > install init scripts. It would be nice to have a concise set of installation > instructions that leverage those scripts. I put together a list of > instructions the other day for one of our installs, that is included below. > It needs review, testing, and integration into the standard docs (user manual > + README in some form). > 1. Accumulo 1.5.x should be installed using the scripts in the scripts > directory under ACCUMULO_HOME, which should be /usr/lib/accumulo. Make a > symbolic link to the /usr/lib/accumulo_1.5.0 directory (or whatever version > you're using), which is where you should put the package. > 2. Zookeeper must be installed on all machines, but it only needs to be > running on the zookeeper nodes. > 3. Make sure the HDFS /user/accumulo exists and is owned by the accumulo user > (for the trash collection issue). > 4. Make sure dfs.durable.sync (or dfs.support.append on some platforms) is > enabled. Reboot HDFS after this is set. > 5. For Accumulo with encryption, use the encryption settings from > conf/examples/crypto/accumulo-site.xml, but the other settings from > conf/examples/3GB/native-standalone* for performance. You can also bump up > the memory settings for cache and memory maps according to resources > available on the cluster. > 6. Make sure to set the instance.secret using a password generator. > 7. Make sure the accumulo-site.xml is set to only be readable by the accumulo > user. > 8. Change the accumulo-monitor user to accumulo (substitute accumulo for > accumulo_monitor in lines 28, 31, 35 of scripts/monitor-only-init.sh). This > is one way of getting past the security restrictions on the accumulo-site.xml > file and on the accumulo directory in HDFS. An alternative would be to give > the accumulo_monitor user access to those resources. > 9. From the scripts directory, run ./master-only-init.sh, ./gc-only-init.sh, > and ./monitor-only-init.sh on the master node. > 10. chown -R accumulo /usr/lib/accumulo* > 11. scp or rsync the configured accumulo directory through the cluster > 12. From the scripts directory, run ./tserver-only-init.sh on each of the > tservers. > 13. Start up all the processes using "service accumulo-master start" or the > appropriate commands on each server. > 14. Check that all the processes started using jps -m, and check that the > right number of tservers started on the monitor page. > 15. Test! Accumulo shell first, then CI if you're ambitious. > 16. Monitor the logs via the monitor page periodically over the next half > hour to see if there are any errors or warnings. Some things don't cause > errors at the API level for a while, but they show up earlier in the logs. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2979) org.apache.accumulo.test.functional.WatchTheWatchCountIT.test failed
[
https://issues.apache.org/jira/browse/ACCUMULO-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060794#comment-14060794
]
Josh Elser commented on ACCUMULO-2979:
--
My jenkins died on Friday and I didn't realize it until today, so no, I haven't
seen any more failures of it yet.
> org.apache.accumulo.test.functional.WatchTheWatchCountIT.test failed
>
>
> Key: ACCUMULO-2979
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2979
> Project: Accumulo
> Issue Type: Bug
> Components: test
>Reporter: Josh Elser
>Assignee: Eric Newton
>Priority: Minor
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> Stacktrace
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.accumulo.test.functional.WatchTheWatchCountIT.test(WatchTheWatchCountIT.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (ACCUMULO-2979) org.apache.accumulo.test.functional.WatchTheWatchCountIT.test failed
[
https://issues.apache.org/jira/browse/ACCUMULO-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060787#comment-14060787
]
Eric Newton commented on ACCUMULO-2979:
---
Is this still failing? Do you have the watcher count on your system?
> org.apache.accumulo.test.functional.WatchTheWatchCountIT.test failed
>
>
> Key: ACCUMULO-2979
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2979
> Project: Accumulo
> Issue Type: Bug
> Components: test
>Reporter: Josh Elser
>Assignee: Eric Newton
>Priority: Minor
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> Stacktrace
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.accumulo.test.functional.WatchTheWatchCountIT.test(WatchTheWatchCountIT.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACCUMULO-2991) Incorrect character in zookeeper-loss administration section
[
https://issues.apache.org/jira/browse/ACCUMULO-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-2991:
Description:
On http://accumulo.apache.org/1.6/accumulo_user_manual.html#zookeeper_failure
{noformat}
For example, to process the table with an ID of 1, make a new directory, say
/new-table-1 and then copy all files from /accumulo/tables/1//.rf into that
directory.
{noformat}
The path should read {{/accumulo/tables/1/\*/\*.rf}}. It appears that the
asterisk is being interpreted as a special character instead of a literal.
was:
On http://accumulo.apache.org/1.6/accumulo_user_manual.html#zookeeper_failure
{noformat}
For example, to process the table with an ID of 1, make a new directory, say
/new-table-1 and then copy all files from /accumulo/tables/1//.rf into that
directory.
{noformat}
The path should read {{/accumulo/tables/1/*/*.rf}}. It appears that the
asterisk is being interpreted as a special character instead of a literal.
> Incorrect character in zookeeper-loss administration section
>
>
> Key: ACCUMULO-2991
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2991
> Project: Accumulo
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.6.0
>Reporter: Josh Elser
>Priority: Trivial
> Labels: newbie
> Fix For: 1.6.1, 1.7.0
>
>
> On http://accumulo.apache.org/1.6/accumulo_user_manual.html#zookeeper_failure
> {noformat}
> For example, to process the table with an ID of 1, make a new directory, say
> /new-table-1 and then copy all files from /accumulo/tables/1//.rf into that
> directory.
> {noformat}
> The path should read {{/accumulo/tables/1/\*/\*.rf}}. It appears that the
> asterisk is being interpreted as a special character instead of a literal.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
