mum
> allowable buffer size for ALL connections.
>
>
>
> Is there a setting that I can increase to get past it?
>
>
>
> -S
>
>
>
>
> --
>
> *From:* Ligade, Shailesh [USA]
> *Sent:* Tuesday, March 15, 2022 12:47 PM
> *
g that I can increase to get past it?
>
> -S
>
>
> --
> *From:* Ligade, Shailesh [USA]
> *Sent:* Tuesday, March 15, 2022 12:47 PM
> *To:* user@accumulo.apache.org
> *Subject:* Re: [External] Re: odd issue with accumulo 1.10.0 starting up
>
> Not daily but over weekend.
> -
e not crashing themselves.
>
> I guess worst case, i can re-initialize and recreate tables form hdfs..:-(
>
> -S
> --
> *From:* Mike Miller
> *Sent:* Tuesday, March 15, 2022 9:16 AM
> *To:* user@accumulo.apache.org
> *Subject:* Re: [External] Re:
nning in AWS, node running accumulomaster also hosts
> comet head node. In current deployment, EC2 instance is of type small which
> has 2GB ram. Issue: Accumulomaster process is kil...
> github.com
>
>
> -S
>
> --
> *From:* Mike Miller
>
Check your configuration. The log message indicates that there is a problem
with the internal system user performing operations. The internal system
user uses credentials derived from the configuration (such as the
instance.secret field). Make sure your configuration is identical across
all nodes i
You can set Java -D options in the accumulo-env.sh script.
On Fri, Jan 21, 2022 at 8:48 AM Ligade, Shailesh [USA] <
ligade_shail...@bah.com> wrote:
> uhmm I didn't see any -D option on shell
>
> if I try
>
> bin/accumulo -Dlog4j.configuration=/tmp/log4j.properties shell - throws
> error as it is
d thus having that setting high enough will make things faster to
> recover.
>
>
>
> Thanks
>
>
>
> -S
>
>
>
> *From:* Mike Miller
> *Sent:* Thursday, December 2, 2021 10:39 AM
> *To:* user@accumulo.apache.org
> *Subject:* Re: [External] Re: [EXTERNAL EMAIL
)
>
>
>
> This setting appears to be working on accumulo 2.0.1, but since that is
> not my prod version I have not tested it completely.
>
>
>
> Thanks
>
>
>
> -S
>
> *From:* Mike Miller
> *Sent:* Thursday, December 2, 2021 9:38 AM
> *To:* user@accum
When you say "since that setting (table.suspend.duration) is not working
for me in accumulo 1.10.0" do you mean that the feature is not helping to
solve your problem? Or that the feature is not working and there could be a
bug?
On Thu, Dec 2, 2021 at 8:00 AM Ligade, Shailesh [USA] <
ligade_shail..
Are you using Log4j? Log4j has
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/RollingFileAppender.html
On Tue, Nov 23, 2021 at 11:15 AM Ligade, Shailesh [USA] <
ligade_shail...@bah.com> wrote:
> Hello,
>
> Currently logs (all tserver, master) are getting huge and sometimes fills
>
riginally set to 3.6.2 just like you said. It didn’t download,
> hence my troubles. I’ll try again with a fresh checkout.
>
>
>
> Like I said, it appears on the surface of it that 3.6.2 is no longer
> available.
>
>
>
> *From: *Mike Miller
> *Date: *Friday,
What do you have set in your /conf/uno.conf ?
If you have the ZK version set like this: export
ZOOKEEPER_VERSION=${ZOOKEEPER_VERSION:-3.6.2}
Then it shouldn't have any problem downloading it automatically for you.
The first mirror that mine failed but the second one worked fine.
11:00:01 {main} ~/
The short answer is no, I don't know of anything like that sorry. The only
documentation I found that is close is some tips in the user manual about
physical memory:
https://accumulo.apache.org/1.10/accumulo_user_manual.html#_physical_memory
The long answer is that it will depend on many factors i
> Do we have updated documentation for influxdb 2 and grafana 7+?
There is nothing on the Accumulo website, no. Others in the community who
have used them may be able to provide some links.
> Also is there any weburl, for accumulo 1.10...
Not for that version. The monitor was redesigned in 2.X t
The admin stop command issues a graceful shutdown to Accumulo for that
tserver. There is a force option you could try {"-f", "--force"} that will
remove the lock. But these are more graceful than a linux kill -9 command,
which you may have to do if the admin command doesn't kill the process
entirel
You may be able to get away with using the same file but I wouldn't
recommend it. You would be introducing an unnecessary risk since every
release is tested against the build for that release. The safest way would
obviously be to upgrade the native files as well when you do the upgrade.
The build
elete since their IDs in the metadata are
> lower than currently created ones and the ID doesn’t appear in tables –l
>
>
>
> I like your GC idea I will look into that. I may have cloned tables in
> the past to fix some other problem but it is not something I would normally
Was Accumulo still starting up? I think these errors are common if the
Monitor starts up before the Master is ready.
On Mon, Jan 11, 2021 at 9:08 AM Jansen, Jerome [USA]
wrote:
> I noticed that the accumulo monitor page did not display any INFO or
> Warning messages.
> I checked the logs for th
This interface is not technically a part of the user API (see
https://accumulo.apache.org/api/) but it is a component that was designed
to be pluggable before Accumulo had a clean API. There are a lot of issues
with these pluggable interfaces, one of them being that they use internal
components th
her (presumably defunct)
>> tablets with unassigned problems in tables that no longer exist.
>>
>>
>>
>> There are warnings in the documentation about manually editing the
>> accumulo metadata table but it seems that the only option is to go in with
>> a d
ave found that there
> are deleted tables that still have a lot of tablets in the metadata table.
>
> I need to solve that before coming back to find the 1 unloaded tablet.
>
>
>
> Cheers And.
>
>
>
> *From:* Mike Miller
> *Sent:* 24 September 2020 16:08
> *
tries in the table.
>
>
>
> *From:* Mike Miller
> *Sent:* 24 September 2020 15:10
> *To:* user@accumulo.apache.org
> *Subject:* Re: Continuous tablets unloaded and fails to balance from
> accumulo master
>
>
>
> EXTERNAL SENDER: Do not click any links or open any
You should be able to figure out the unloaded tablet from the
"accumulo.metadata" table. The metadata table will list the tablet
location using the "loc" column family to indicate it has loaded a tablet
that it was assigned.
For example the tablet "n;9" will have an entry like:
n;9 loc:141fbf0
The Accumulo ITs (any java files whose name ends in IT) would be a good
example since they are all run using MiniAccumuloCluster, with some being
able to run against a standalone cluster[1]. Some ITs start and stop a
cluster for every test, while others keep a cluster running for the whole
IT. An
ef
> wrote:
> >
> > We are using the built in crypto strategy :
> CachingHDFSSecretKeyEncryptionStrategy with the cypher suite
> AES/CFB/NoPadding
> >
> >
> >
> >
> >
> >
> >
> > De : Mike Miller
> > Envoyé le :lundi 21 octobr
Hi Cyrille - This could be a number of issues. The Key could be wrong, the
block could not finished writing to the WAL when you shutdown, etc...
What type of crypto do you have setup? Are you using the built in crypto
strategies or did you write your own?
On Mon, Oct 21, 2019 at 3:36 PM Cyrille
IteratorUtil was an internal class, not part of the public API. There was
some work done in 2.0 to migrate some of the internals out of IteratorUtil
so it could be part of the API but it is not quite there yet. The method
you are looking for is probably in
org.apache.accumulo.core.conf.IterConfig
Some tips from Ed:
The key is what shows up in the metadata - if you look at the System Metadata
tables section in the Accumulo user’s manual, the files entries have a form of
row_id, filename, file_size, row_count.
The monitor is reflecting what the the metadata table is showing. In the case
The entries should show up regardless of auths but are really just an
estimate. The Monitor gets that information from what the Master has in
memory so may not reflect recent activity such as bulk imports or
deletions. A compaction of the table should make that more accurate.
On Thu, Oct 3, 2019
Yes it has been pulled from the main Accumulo 2.0 repository. The proxy is
now in its own repo here: https://github.com/apache/accumulo-proxy
It should still work the same.
On Thu, Aug 29, 2019 at 10:17 AM Roberts, Geoffry [USA] <
roberts_geof...@bah.com> wrote:
> I hope this is a quick question
The Apache Accumulo project is pleased to announce the release of
Apache Accumulo 2.0.0! Apache Accumulo 2.0.0 contains many new
features, bug fixes, performance improvements and redesigned
components. Hadoop 3 and Java 8 are required for this version.
New users are encouraged to start using 2.0
I can't say I have done it personally but 1.8 and 1.9 are very similar so
you "shouldn't" have any problems.
Here are the upgrade instructions:
https://accumulo.apache.org/docs/2.x/administration/upgrading
On Mon, Jun 10, 2019 at 2:33 PM Bulldog20630405
wrote:
>
> i did not see any upgrading in
The Apache Accumulo project is pleased to announce the release of
Apache Accumulo
1.9.3! Apache Accumulo 1.9.3 contains bug fixes for Write Ahead Logs and
compaction. Users of 1.9.2 are encouraged to upgrade. (See the release
notes linked below for details.)
Users of Versions of 1.9 and 1.8 are en
Measuring scan performance by piping output from the shell is not the best
way. A lot of time is wasted printing output to the terminal. You are
better off measuring the difference using the Batch Scanner API directly.
An example can be found here:
https://accumulo.apache.org/tour/batch-scanner/
Off the top of my head, I am not sure what to do for your problem. But we
have released native packages for Fedora here:
https://src.fedoraproject.org/rpms/accumulo/tree/master
Perhaps the work we did to support those packages might help.
On Wed, Aug 8, 2018 at 3:32 AM Maria Krommyda wrote:
> H
Quick Survey:
Does your project use the flush Table Operation in Accumulo? I am looking
into changing the default behavior of the deprecated flush method[1] and
was wondering if and how it is currently being used.
Any response would be helpful. Thanks!
[1]
https://github.com/apache/accumulo/blo
36 matches
Mail list logo
