Re: RIAK Roadmap Workshop

2017-09-22 Thread Mark Allen
 I also wanted to raise the profile on the work that Ted worked on providing 
substantially better visibility and control into the tasks which vnodes are 
asked to schedule, execute and return from:
https://github.com/basho/riak_core/pull/895

This is the WIP tracking branch with the design, prototype code, etc.  This is 
an important effort to able to track "bad queries" from consuming an entire 
node's worth of resources.
On Saturday, September 23, 2017, 2:32:35 AM GMT+1, Fred Dushin 
 wrote:  
 
 Thank you, Andrew, and Bet365 for hosting this event, and for shepherding Riak 
through these difficult times.
I will not be able to attend, but under enhancements, I would encourage the 
group to discuss the late enhancements to Riak/KV to support efficient bucket 
and key listing for sorted back ends.  This work can be found on the develop 
and develop-2.2 branches of riak_kv; it was not formally shipped in any Basho 
production releases, but listing buckets has seen some testing (and the code 
changes are relatively small).
Listing buckets in time proportional to the number of buckets (not the number 
of keys in the cluster), and keys in a bucket proportional to the number of 
keys in the bucket (not the number of keys in the cluster) seems like a 
laudable goal for which I am sure customers would find use cases.  Key listing 
has always been an operation known to kill large clusters, and the advice has 
always been, "don't do that", despite its obvious utility.  With these changes, 
that advice can be dropped for a subset of users.
-Fred
https://github.com/basho/riak_kv/pull/1634https://github.com/basho/riak_kv/pull/1650

On Sep 22, 2017, at 9:56 AM, andrew.de...@bet365.com wrote:
 Hi, We are beginning to plan out the two day workshop [1]. We are thinking the 
first day will start with an introduction from Martin Davies, in which Martin 
will detail current status and the asset list.  After which we will get into 
project questions, such as: Which license?The general consensus is Apache2. We 
need to complete the discussion as HyperLogLog has been introduced which is 
GPL’d. Our thoughts are to replace HLL. Baseline?We have heard some discussion 
around where to baseline the codebase. The concern is during the demise of 
Basho the correct level of diligence was not applied to promotes meaning the 
code such as HLL has crept in.  Governance?How are we to manage the project 
going forward? Our feeling is we do not need a formal body as being discussed 
in the slack group. We see the project going forward as a simple repo into 
which likeminded developers agree and contribute changes. Placing overbearing 
procedure and structure on what is currently a small community will dissuade 
other from joining and contributing. Supporting infrastructure.The Basho 
websites, github account, and mailing group are all included in the deal. We 
are currently supporting the mailing list, and once the deal is complete we 
will continue to support the Basho domains; restricting community disruption. 
RoadmapBelow, in no particular order, are the items we wish to address 
internally. If we can all share our lists we can come to an agreed community 
roadmap between us. · Review / rationalisation of Basho JIRA tickets / 
git issues · ReplicationoAddress known issues (30+) to add 
stabilityoSelective replicationoPersistent realtime queueoReview of 
general approach§  In / out of band§  Snapshot vs deltas · Generalo
Address known issues (20+) to add stabilityoSilent data loss bug in riak_kv 
· EnhancementsoG SetsoBig SetsoCRDT MapsoAsync read / 
write vnodesoSplit backend vnodesoHead requests – don’t return body to 
co-ordinatoroRudimentary indexing (leverage TS work) · 
Consolidation / feature cross population of KV,CS, and TS codebases · 
Erlang / OTP upgrade  At this point we want to keep the structure of the day 
loose to allow the conversations to flow, our collective priorities to take 
precedence. The sessions will be live streamed, with details to follow. We will 
also man IRC / Slack for discourse. Food and refreshments will be provided 
throughout the two days. Hopefully this gives us something to discuss in the 
build up to the 12th Oct. We’re looking for everyone’s input so we can hit the 
ground running. As a quick update on the status of the purchase. We have 
exchanged funds and the court process continues. One clarifying point for 
anyone following the court proceedings. The purchasing company is our 
technology arm, Hillside Technology Limited, not the bet365 group. Thanks,Andy. 
 [1] https://www.meetup.com/RIAK-Development-Roadmap-Workshop/events/243302656/ 
  
| Andrew Deane |
| Systems Development Manager - Middleware |
| Hillside (Technology) Limited |
| andrew.de...@bet365.com |
| bet365.com |

 This email and any files transmitted with it are confidential and contain 
information which may be privileged or 

Re: Riak London meetup - Bet365 presenting

2017-09-11 Thread Mark Allen
 Wish I could make it. Would definitely be interested in the video.
Thanks.
On Monday, September 11, 2017, 5:11:46 AM CDT, Steve Roberts 
 wrote:  
 
 Hi all

We are hosting  a meetup in London this Thu 14th where Bet365 are 
presenting about Riak.  We have a few spaces left if you are interested 
in attending.  We hope to video the session and share for those who are 
unable to attend.

https://www.meetup.com/riak-london/events/243169582/

Regards
Steve


___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
  ___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Late to the party but still wish to compile a working Riak

2017-07-17 Thread Mark Allen
Just to follow up on this, I tried to work out OTP 20 support tonight but it 
looks like riak_ensemble is going to need some serious TLC to get OTP 20 to 
compile on it due to its use of deprecated gen_fsm calls in various parts of 
the application.  
So I'm going to omit support for OTP 20 for now and work on OTP 18 and 19 
support tomorrow for udon. That ought to be quite a bit more straight forward. 
I think it would mostly entail adding the proper relx configuration.
Mark

On Monday, July 17, 2017, 12:41:04 PM CDT, Mark Allen  
wrote:

OK, I see that the project doesn't seem to support OTP 18, 19 or 20. I'll see 
if I can bump the deps and get it working using Heinz's fork tonight US time.On 
Monday, July 17, 2017, 12:38:07 PM CDT, Mark Allen  wrote:

You might want to consider starting with udon, my "learn riak core" application 
I wrote a couple years ago:
http://basho.com/posts/technical/understanding-riak_core-building-handoff/

https://speakerdeck.com/mrallen1/building-distributed-applications-with-riak-core

https://github.com/mrallen1/udon

Happy to answer questions here, via twitter @bytemeorg, or github issues, or in 
irc on #riak (might be slow - I don't look at riak-user constantly.)
Mark

On Monday, July 17, 2017, 11:16:01 AM CDT, David Bloom  
wrote:

Hello Riak list!  After watching many videos about Erlang and LFE in particular 
I think I get it and now understand the many benefits of the BEAM and thought 
that Riak would make an excellent tool to build applications with.
While getting excited I learned of Basho's current limbo status but still 
interested in learning Riak as it has already been adopted enough that it seems 
that Riak (or it's future open-source name whatever) is here to stay.
How can I compile a working Riak?  Is it daft of me to learn Erlang/LFE to get 
future work supporting existing Riak installations?  Though very new to the 
Erlang ecosystem, I've managed to use Kerl to install different versions of R16 
and R17, even used it to install Basho's patched R16 but nothing works.
Would it be better to try using the existing Riak containers on Docker Hub?  
Any thoughts or tips for a Lisper looking to work with and learn more Erlang?  
My resume available upon request.  Thanks in advance for your help.
-David Bloom___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Late to the party but still wish to compile a working Riak

2017-07-17 Thread Mark Allen
Personally, I learn best by experimenting with code, so that's what I like to 
try to do next but, either option is good.  Go with what feels most comfortable 
for you. :-)

On Monday, July 17, 2017, 12:51:34 PM CDT, David Bloom  
wrote:

Thank you Mark.  I look forward to absorbing as much material as I can.  Your 
articles on Udon look like a great starting point after completing LYSE book.  
Would you recommend completing erlang in anger book as well before diving into 
code or LYSE and just dive into it straight away?
David

On Jul 17, 2017 1:40 PM, "Mark Allen"  wrote:

OK, I see that the project doesn't seem to support OTP 18, 19 or 20. I'll see 
if I can bump the deps and get it working using Heinz's fork tonight US time.On 
Monday, July 17, 2017, 12:38:07 PM CDT, Mark Allen  wrote:

You might want to consider starting with udon, my "learn riak core" application 
I wrote a couple years ago:
http://basho.com/posts/technic al/understanding-riak_core- building-handoff/

https://speakerdeck.com/mralle n1/building-distributed-applic 
ations-with-riak-core

https://github.com/mrallen1/ud on

Happy to answer questions here, via twitter @bytemeorg, or github issues, or in 
irc on #riak (might be slow - I don't look at riak-user constantly.)
Mark

On Monday, July 17, 2017, 11:16:01 AM CDT, David Bloom  
wrote:

Hello Riak list!  After watching many videos about Erlang and LFE in particular 
I think I get it and now understand the many benefits of the BEAM and thought 
that Riak would make an excellent tool to build applications with.
While getting excited I learned of Basho's current limbo status but still 
interested in learning Riak as it has already been adopted enough that it seems 
that Riak (or it's future open-source name whatever) is here to stay.
How can I compile a working Riak?  Is it daft of me to learn Erlang/LFE to get 
future work supporting existing Riak installations?  Though very new to the 
Erlang ecosystem, I've managed to use Kerl to install different versions of R16 
and R17, even used it to install Basho's patched R16 but nothing works.
Would it be better to try using the existing Riak containers on Docker Hub?  
Any thoughts or tips for a Lisper looking to work with and learn more Erlang?  
My resume available upon request.  Thanks in advance for your help.
-David Bloom__ _
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman /listinfo/riak-users_lists. basho.com
__ _
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman /listinfo/riak-users_lists. basho.com


___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Late to the party but still wish to compile a working Riak

2017-07-17 Thread Mark Allen
OK, I see that the project doesn't seem to support OTP 18, 19 or 20. I'll see 
if I can bump the deps and get it working using Heinz's fork tonight US time.On 
Monday, July 17, 2017, 12:38:07 PM CDT, Mark Allen  wrote:

You might want to consider starting with udon, my "learn riak core" application 
I wrote a couple years ago:
http://basho.com/posts/technical/understanding-riak_core-building-handoff/

https://speakerdeck.com/mrallen1/building-distributed-applications-with-riak-core

https://github.com/mrallen1/udon

Happy to answer questions here, via twitter @bytemeorg, or github issues, or in 
irc on #riak (might be slow - I don't look at riak-user constantly.)
Mark

On Monday, July 17, 2017, 11:16:01 AM CDT, David Bloom  
wrote:

Hello Riak list!  After watching many videos about Erlang and LFE in particular 
I think I get it and now understand the many benefits of the BEAM and thought 
that Riak would make an excellent tool to build applications with.
While getting excited I learned of Basho's current limbo status but still 
interested in learning Riak as it has already been adopted enough that it seems 
that Riak (or it's future open-source name whatever) is here to stay.
How can I compile a working Riak?  Is it daft of me to learn Erlang/LFE to get 
future work supporting existing Riak installations?  Though very new to the 
Erlang ecosystem, I've managed to use Kerl to install different versions of R16 
and R17, even used it to install Basho's patched R16 but nothing works.
Would it be better to try using the existing Riak containers on Docker Hub?  
Any thoughts or tips for a Lisper looking to work with and learn more Erlang?  
My resume available upon request.  Thanks in advance for your help.
-David Bloom___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Late to the party but still wish to compile a working Riak

2017-07-17 Thread Mark Allen
You might want to consider starting with udon, my "learn riak core" application 
I wrote a couple years ago:
http://basho.com/posts/technical/understanding-riak_core-building-handoff/

https://speakerdeck.com/mrallen1/building-distributed-applications-with-riak-core

https://github.com/mrallen1/udon

Happy to answer questions here, via twitter @bytemeorg, or github issues, or in 
irc on #riak (might be slow - I don't look at riak-user constantly.)
Mark

On Monday, July 17, 2017, 11:16:01 AM CDT, David Bloom  
wrote:

Hello Riak list!  After watching many videos about Erlang and LFE in particular 
I think I get it and now understand the many benefits of the BEAM and thought 
that Riak would make an excellent tool to build applications with.
While getting excited I learned of Basho's current limbo status but still 
interested in learning Riak as it has already been adopted enough that it seems 
that Riak (or it's future open-source name whatever) is here to stay.
How can I compile a working Riak?  Is it daft of me to learn Erlang/LFE to get 
future work supporting existing Riak installations?  Though very new to the 
Erlang ecosystem, I've managed to use Kerl to install different versions of R16 
and R17, even used it to install Basho's patched R16 but nothing works.
Would it be better to try using the existing Riak containers on Docker Hub?  
Any thoughts or tips for a Lisper looking to work with and learn more Erlang?  
My resume available upon request.  Thanks in advance for your help.
-David Bloom___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: [ANN] Basho move Lager to erlang-lager organization on Github

2016-12-05 Thread Mark Allen
Just to follow up on this: 
Andrew Thompson and I are going to start hosting a monthly lager issue/PR 
triage meeting on freenode, in #lager every third Thursday of the month 
starting 19 January 2017 at 1600 US/Central time, 1400 US/Pacific time, 2200 
UTC for about an hour or so.
During that time, we will review open pulls, open issues and generally be 
available via IRC to answer questions.  If you have questions about lager, or 
want to help, please join us.
In the meantime, I hope to groom the current PRs/issues during the upcoming 
holidays so that we can enter January with a nice clean start for the new year.
Many many thanks to Basho and Doug for making this happen! 
Cheers,
Mark___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Cluster ready status for Riak S2

2016-03-31 Thread Mark Allen
You could try a `riak-cs ping` command and make sure it gets a "pong" response 
as output.  That's not a solid guarantee that everything's totally started, but 
its better than just sleeping and hoping for the best.
Mark 

On Monday, March 28, 2016 10:13 AM, Jhonny Everson  
wrote:
 

 Hi,I am starting riak-cs for integration tests in a docker container. Does 
anyone know if there is a stat I can use to make sure it is fully started 
before using it? I am currently waiting(sleep) 30s for it to start but ideally 
I could check for a status and continue once it is ready.

-- 
Jhonny Everson
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


  ___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Riak Go Client 1.1 is Available!

2015-08-30 Thread Mark Allen
Cool! Great work!!

Sent from my iPhone

> On Aug 27, 2015, at 11:21 PM, Alex Moore  wrote:
> 
> Hi All,
> 
> The Go client for Riak is out of beta, so Go get it!
> 
> To install it in your go project, just run `go get 
> github.com/basho/riak-go-client`.
> 
> You can find more information on the project page 
> (https://github.com/basho/riak-go-client), and in the API docs 
> (https://godoc.org/github.com/basho/riak-go-client).
> 
> Special thanks to Luke Bakkan & Chris Mancini for their work on the client, 
> Timo Gatsonides for his inspiring work on goriakpbc, and Sergio Arteaga for 
> submitting GitHub issues.
> 
> Thanks,
> Alex
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Lager 3.0 coming soon

2015-06-01 Thread Mark Allen
(Sorry if you already saw this on erlang-questions. But on the off chance you 
don't read it...)

Basho has been working on an update[1] to lager to support multiple event sinks 
so different behaviors can be configured based on type of message. Security 
audit information, for example, may have different needs than general event 
messages. 

Because this introduces some subtle backwards compatibility issues with lager's 
tracing mechanism, we're going to roll this into a new major version of lager, 
3.0, along with several community PRs[2].

Specifically, the backwards compatibility problems with tracing: 
* Traces are sink-specific and thus will not be able to see messages destined 
for other sinks 
* Tracing to a log file that is already open for lager will only work if 
targeting the same sink; otherwise an error will be returned to the trace 
request 

If you're curious about the performance impact of these changes, we have been 
benchmarking our work. The results look good.[3]

We are also opening a maintenance 2.x branch with updates (and a few bug fixes) 
for the current 2.1.1 release which includes support and test suite fixes for 
OTP 17 but without any of the new 3.0 semantics/behavior.[4]

If you'd like to kick the tires, we have tagged a 3.0.0 release candidate[5], 
which should make it easy for you to take it for a spin.

Please feel free to contact us with thoughts on lager 3.0, either via GitHub 
issues/comments on PRs or by replying to this thread. 

Thanks!

[1]: https://github.com/basho/lager/pull/264
[2]: https://github.com/basho/lager/pull/270
[3]: https://gist.github.com/mrallen1/681b2b0f0e55e56e8e29
[4]: https://github.com/basho/lager/pull/269
[5]: https://github.com/basho/lager/releases/tag/3.0.0-RC1

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Python 2.6 support?

2014-07-02 Thread Mark Allen
Late to the party, but a bunch of our servers are stuck at python 2.6 (debian 
squeeze), so please don't drop support for it.

Thank you.

Mark


On Wednesday, June 25, 2014 2:10 PM, Sean Cribbs  wrote:
 


In the process of developing the Python client for 2.0 features, we're running 
into issues with Python 2.6.x (specifically related to pyOpenSSL and its 
dependencies). Is anyone out there using Python 2.6 in production still and 
wanting to use the Riak client?

-- 
Sean Cribbs 
Software Engineer
Basho Technologies, Inc.
http://basho.com/
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Riak 1.4x counter examples using riakc (erlang-riak-client)

2013-11-20 Thread Mark Allen
Hi -

I'm trying to puzzle through how to use the PN counters in Riak 1.4.x via the 
riakc client.  It *looks* like
a 1.4 counter is a special kind of riak_obj metadata tuple.  So do you just set 
the tuple in a riakc_obj with
an undefined value?

The README in the client repo also doesn't seem to have an PN counter examples. 
 Any guidance would
be appreciated.

Thanks.

Mark___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com