Init accumulo with custom properties file

["Samudrala, Ranganath [USA] via user" <us...@accumulo.apache.org>]

Hello

I see there is an option to start an Accumulo component with a different properties file using -p, -props or --props option. Any reason same feature does not exist while performing init?

The problem I am trying to solve is as below:
I am trying to configure Accumulo with S3 using instructions here:  https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html . This instructions calls for following steps:

  1.  Run "init" or "init --upload-accumulo-props"
  2.  Run "init --add-volumes" option
  3.  Start all Accumulo components.

I am trying to configure the setup in K8S and would like to merge all these steps into one deployment invocation task. In K8S, we can attempt to do the first two steps using "initContainers" but the "accumulo.properties" need to be different for each step. So, let us say, I create 2 properties files, accumulo-init.properties and accumulo.properties. In the first step we should be able to specify accumulo-init.properties and for remaining steps, we should be able to use accumulo.properties.

Problem is there is no option to specify a property file during the "init" process.

thanks
Ranga

Re: Init accumulo with custom properties file

[Christopher <ct...@apache.org>]

We certainly could add that feature. The `init` command is kind of a
special utility, and its command-line argument parsing is probably
older, written before the `-p` option was added to the server
processes' command-line argument parsing. But, if it doesn't work, it
can be made to. In the meantime, you could probably just execute the
command with your preferred configuration file higher on the class
path, as in `CLASSPATH="/path/to/preferred/accumulo.properties/parentdir/"
bin/accumulo init` (or edit your accumulo-env.sh script to customize
your CLASSPATH for the `init` command). I haven't tried this... but I
think it should work... let us know if you find this approach works
for you.

I am curious why you're running init, immediately followed by
add-volumes, though. I am wondering why you don't have the volumes
added at the beginning, if you know up front that they are there...
but perhaps I am misunderstanding, and you are running add-volumes
much later? add-volumes isn't usually an initial step, but a step
taken later as maintenance to grow/modify an existing cluster. I'm
curious how your situation matches up to this intent, or if you're
doing something we haven't thought of before.


On Thu, Feb 2, 2023 at 4:11 PM Samudrala, Ranganath [USA] via user
<us...@accumulo.apache.org> wrote:
>
> Hello
>
> I see there is an option to start an Accumulo component with a different properties file using -p, -props or --props option. Any reason same feature does not exist while performing init?
>
> The problem I am trying to solve is as below:
> I am trying to configure Accumulo with S3 using instructions here:  https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html . This instructions calls for following steps:
>
> Run "init" or "init --upload-accumulo-props"
> Run "init --add-volumes" option
> Start all Accumulo components.
>
> I am trying to configure the setup in K8S and would like to merge all these steps into one deployment invocation task. In K8S, we can attempt to do the first two steps using "initContainers" but the "accumulo.properties" need to be different for each step. So, let us say, I create 2 properties files, accumulo-init.properties and accumulo.properties. In the first step we should be able to specify accumulo-init.properties and for remaining steps, we should be able to use accumulo.properties.
>
> Problem is there is no option to specify a property file during the "init" process.
>
> thanks
> Ranga
>

RE: Init accumulo with custom properties file

[dl...@comcast.net]

Take a look at https://github.com/dlmarion/accumulo-k8s. You can put the
Accumulo config in a ConfigMap (accumulo-config.yaml), then mount it at the
correct location in another container (see the server process yaml files). I
used a job to do the init phase, see accumulo-init.yaml.

 

 

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org> 
Sent: Thursday, February 2, 2023 4:11 PM
To: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>
Subject: Init accumulo with custom properties file

 

Hello

 

I see there is an option to start an Accumulo component with a different
properties file using -p, -props or --props option. Any reason same feature
does not exist while performing init?

 

The problem I am trying to solve is as below: 

I am trying to configure Accumulo with S3 using instructions here:
https://accumulo.apache.org/blog/2019/09/10/accumulo-S3-notes.html . This
instructions calls for following steps:

1.	Run "init" or "init --upload-accumulo-props" 
2.	Run "init --add-volumes" option
3.	Start all Accumulo components. 

I am trying to configure the setup in K8S and would like to merge all these
steps into one deployment invocation task. In K8S, we can attempt to do the
first two steps using "initContainers" but the "accumulo.properties" need to
be different for each step. So, let us say, I create 2 properties files,
accumulo-init.properties and accumulo.properties. In the first step we
should be able to specify accumulo-init.properties and for remaining steps,
we should be able to use accumulo.properties. 

 

Problem is there is no option to specify a property file during the "init"
process.

 

thanks

Ranga